Skip to main content

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: Jira POST /search (type=Epic) → child issue progress → Mavera POST /api/v1/mave/chat → Campaign strategy

Code

Example Output

Error Handling

Epics with zero child issues return 0% progress. Filter them out or flag as “not yet scoped” in the campaign strategy.
Jira status categories (done, indeterminate, new) differ from status names. The code uses statusCategory.key for reliable progress regardless of custom workflows.