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_...

All examples use JIRA_DOMAIN, JIRA_EMAIL, JIRA_API_TOKEN (from Atlassian API Tokens), and MAVERA_API_KEY. Basic Auth header is Authorization: Basic {base64(email:api_token)}. Never commit tokens.

---

Prerequisites

1. Create a Jira API token

   Go to id.atlassian.com/manage-profile/security/api-tokens → Create API Token. Copy immediately — it cannot be viewed again.
2. 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}.
3. Mavera API key

   Get your key from Mavera dashboard.
4. Environment variables

   export JIRA_DOMAIN="yourcompany"
   export JIRA_EMAIL="[e-mail]"
   export JIRA_API_TOKEN="ATATT3xFfGF0..."
   export MAVERA_API_KEY="mvra_live_xxxxx"
   

---

Jobs

#	Job	Jira Data	Mavera Surface	Output
1	Customer-Reported Issues → Persona Pain Points	JQL search (customer-reported label)	Mave Agent + Personas	Pain-point personas
2	Sprint Completion → Release Content	Board sprints + resolved issues	Generate	Release notes + changelog
3	Epic Progress → Campaign Alignment	JQL (type=Epic) + child issues	Mave Agent	Campaign strategy
4	Comment Analysis → 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

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.

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 on sprint_closed instead of polling.
• Mavera credits: Monitor at Dashboard.

All Integrations

Jira Cloud API

Personas

Brand Voice

Generate

Mave Agent