Skip to main content

Customer-Reported Issues → Persona Pain Points

Scenario

Your support and engineering teams label customer-reported issues in Jira, but that pain signal never reaches marketing. This job uses JQL to find issues labeled “customer-reported”, extracts summaries and descriptions, sends the aggregate to Mave Agent for pain-point analysis, then creates enriched personas representing common customer pain patterns. Flow: Jira POST /search (JQL) → aggregate issues → Mavera POST /api/v1/mave/chat (pain point analysis) → POST /api/v1/personas (pain-point personas)

Code

Example Output

Error Handling

Jira returns 400 with errorMessages if JQL is malformed. Common mistakes: unquoted strings with spaces, invalid field names, missing escape for reserved characters. Test JQL in Jira’s issue navigator first.
Jira Cloud uses Atlassian Document Format (ADF) for descriptions — nested JSON, not plain text. The code walks content[].content[].text. Rich content (tables, code blocks) needs deeper traversal.
Jira uses a points-based system — search requests cost more than single-issue reads. The code reads Retry-After and waits. Add 500ms between pages for large result sets.