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.
Epic Progress → Campaign Alignment
Scenario
Epics represent major product initiatives — the kind marketing needs to build campaigns around. This job pulls active epics via JQL, calculates progress as percentage of child issues completed, then sends the data to Mave Agent for a campaign strategy aligned with engineering velocity. Flow: JiraPOST /search (type=Epic) → child issue progress → Mavera POST /api/v1/mave/chat → Campaign strategy
Code
Example Output
Error Handling
Epic Link field name
Epic Link field name
In Jira Cloud, the Epic Link field may use a custom field ID (e.g.
customfield_10014). If JQL fails, query GET /rest/api/3/field to discover the correct name for your instance.Empty epics
Empty epics
Epics with zero child issues return 0% progress. Filter them out or flag as “not yet scoped” in the campaign strategy.
Status category mapping
Status category mapping
Jira status categories (
done, indeterminate, new) differ from status names. The code uses statusCategory.key for reliable progress regardless of custom workflows.