> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> 4 production-ready jobs — customer-reported issue personas, sprint release content, epic-to-campaign alignment, and comment-driven feature messaging

Jira is where engineering teams track every bug, feature, and epic — and that data is a goldmine for marketing. These four jobs pull issue data from Jira's REST API into Mavera (Personas, Mave Agent, Brand Voices, Generate) to build pain-point personas, auto-generate release content from sprints, align campaigns with epic progress, and extract voice-of-the-customer language from comments.

***

## API Reference Card

| Detail            | Value                                                                                               |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| **Base URL**      | `https://{domain}.atlassian.net/rest/api/3`                                                         |
| **Auth**          | Basic Auth (`email:api_token` base64), OAuth 2.0, or JWT                                            |
| **Rate limits**   | Points-based hourly quotas (varies by plan — Free: lower, Premium/Enterprise: higher)               |
| **Key endpoints** | `POST /search` (JQL), `GET /board/{id}/sprint`, `GET /sprint/{id}/issue`, `GET /issue/{id}/comment` |
| **Pagination**    | Offset-based via `startAt` + `maxResults`; max 100 per page                                         |
| **Mavera base**   | `https://app.mavera.io/api/v1`                                                                      |
| **Mavera auth**   | `Authorization: Bearer mvra_live_...`                                                               |

<Info>
  All examples use `JIRA_DOMAIN`, `JIRA_EMAIL`, `JIRA_API_TOKEN` (from [Atlassian API Tokens](https://id.atlassian.com/manage-profile/security/api-tokens)), and `MAVERA_API_KEY`. Basic Auth header is `Authorization: Basic {base64(email:api_token)}`. Never commit tokens.
</Info>

***

## Prerequisites

<Steps>
  <Step title="Create a Jira API token">Go to [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens) → Create API Token. Copy immediately — it cannot be viewed again.</Step>
  <Step title="Identify your domain and project keys">Your domain is the subdomain in `https://{domain}.atlassian.net`. Project keys are issue prefixes (e.g. `PROJ-123`). Board IDs appear in the URL: `rapidView={board_id}`.</Step>
  <Step title="Mavera API key">Get your key from [Mavera dashboard](https://app.mavera.io/settings/api-keys).</Step>

  <Step title="Environment variables">
    ```bash theme={"dark"}
    export JIRA_DOMAIN="yourcompany"
    export JIRA_EMAIL="you@company.com"
    export JIRA_API_TOKEN="ATATT3xFfGF0..."
    export MAVERA_API_KEY="mvra_live_xxxxx"
    ```
  </Step>
</Steps>

***

## Jobs

| # | Job                                                                                          | Jira Data                            | Mavera Surface          | Output                    |
| - | -------------------------------------------------------------------------------------------- | ------------------------------------ | ----------------------- | ------------------------- |
| 1 | [Customer-Reported Issues → Persona Pain Points](/integrations/jira/customer-issue-personas) | JQL search (customer-reported label) | Mave Agent + Personas   | Pain-point personas       |
| 2 | [Sprint Completion → Release Content](/integrations/jira/sprint-release-content)             | Board sprints + resolved issues      | Generate                | Release notes + changelog |
| 3 | [Epic Progress → Campaign Alignment](/integrations/jira/epic-campaign-alignment)             | JQL (type=Epic) + child issues       | Mave Agent              | Campaign strategy         |
| 4 | [Comment Analysis → Feature Messaging](/integrations/jira/comment-feature-messaging)         | Issue comments                       | Brand Voices + Generate | Customer-voice messaging  |

***

## Rate Limits & Production Notes

| Plan                 | Rate Limit               | Strategy                                                        |
| -------------------- | ------------------------ | --------------------------------------------------------------- |
| Free                 | Lower hourly point quota | 500ms between calls; minimize JQL result sets                   |
| Standard             | Moderate hourly quota    | Parallel requests OK with retry; use `fields` to slim responses |
| Premium / Enterprise | Higher quotas            | Webhooks for event-driven automation; bulk endpoints            |

<Warning>
  Jira Cloud uses a **points-based** rate limit system — search requests cost more than single-issue reads. Always read the `Retry-After` header on 429 responses (value is in seconds). For production, implement exponential backoff and specify `fields` on every request to minimize response size.
</Warning>

**Production checklist:**

* **Auth**: API tokens inherit user permissions. For team automations, use OAuth 2.0 with a service account.
* **Pagination**: Max 100 items per page. Follow `startAt` + `maxResults` until `startAt >= total`.
* **JQL optimization**: Filter server-side. Always specify `fields` to request only what you need.
* **ADF parsing**: Descriptions and comments use Atlassian Document Format. Use an ADF-to-text library in production.
* **Webhooks**: Register a [Jira webhook](https://developer.atlassian.com/cloud/jira/platform/webhooks/) on `sprint_closed` instead of polling.
* **Mavera credits**: Monitor at [Dashboard](https://app.mavera.io/settings/usage).

<CardGroup cols={3}>
  <Card title="All Integrations" icon="plug" href="/integrations" />

  <Card title="Jira Cloud API" icon="diagram-project" href="https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/" />

  <Card title="Personas" icon="users" href="/features/personas" />

  <Card title="Brand Voice" icon="microphone" href="/features/brand-voice" />

  <Card title="Generate" icon="pen" href="/features/content-generation" />

  <Card title="Mave Agent" icon="brain" href="/features/mave-agent" />
</CardGroup>