Jira sprint report across sprints
“show each jira sprint from the jira sprints and issue sprint history, use story points for carried over points and committed points only for issues not added after start; status below 70% when completion % is under 70, ok otherwise, then list app issues carried over twice or more”
Show each Jira sprint from the Jira sprints and Jira issue sprint history, use story points for carried over points and committed points only for issues not added after start; status below 70% when completion % is under 70, ok otherwise, then list app issues carried over twice or more.
What the agent built
4 steps, each one an ordinary Mammoth step you can open and change.
- FileJira sprintsCSV export · 6 rows
- FileJira issue sprint historyCSV export · 42 rows
- StepMake sprint join key (Jira sprints)Step 1
- StepMake sprint join key (Issue history)Step 2
- JoinAdd issue sprint history6 of 6 paired
- StepCalculate sprint results and carryoversStep 4
- ResultJira Sprint Carryover9 rows · 6 flagged
- ScheduleRuns when you sayProposed
On the sample files, every step runs and the result has 9 rows.
- Download Jira sprints sample (6 rows)Jira: Reports > Sprint Report > Export sprint list
- Download Jira issue sprint history sample (42 rows)Jira: Issues > Search > Export > CSV, with Sprint history fields included
What you get back
The result of that run, the rows to look at first.
| Row type | Sprint | Committed points | Carried over points | Completion % | Status | Issue key | Carryovers | Start date | End date |
|---|---|---|---|---|---|---|---|---|---|
| Sprint | Sprint 38 | 18 | 3 | 38.9 | Below target | · | · | 2026-09-21 | 2026-10-04 |
| Sprint | Sprint 40 | 17 | 0 | 35.3 | Below target | · | · | 2026-10-19 | 2026-11-01 |
| Sprint | Sprint 36 | 18 | 0 | 83.3 | On target | · | · | 2026-08-24 | 2026-09-06 |
| Sprint | Sprint 37 | 21 | 3 | 85.7 | On target | · | · | 2026-09-07 | 2026-09-20 |
| Sprint | Sprint 39 | 20 | 0 | 90 | On target | · | · | 2026-10-05 | 2026-10-18 |
| Sprint | Sprint 41 | 20 | 0 | 90 | On target | · | · | 2026-11-02 | 2026-11-15 |
| Carried-over issue | · | · | · | · | · | APP-201 | 2 | · | · |
| Carried-over issue | · | · | · | · | · | APP-202 | 2 | · | · |
| Carried-over issue | · | · | · | · | · | APP-203 | 2 | · | · |
How it works
How to use the Jira Sprint Carryover workflow
- 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
- 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
- 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.
Jira Sprint Carryover: questions
How do you compare Jira sprints side by side?
What export should you use from Jira?
What happens to rows that do not match?
How do you change the rules?
Get early access to this workflow
It opens already built and working on sample files. Swap in your own exports to see your result.
Workflows like this
The number you report every month, rebuilt from the latest export, plus the forecast that follows from it.
- Customer lifetime value by cohortWork out customer lifetime value by signup month cohort from Shopify customers and orders exports, with revenue per customer and average order count.See the workflow Built by the agent
- Profit and loss by monthBuild a monthly profit and loss statement from a QuickBooks general ledger export, with revenue, COGS, gross profit, expenses, and net income.See the workflow Built by the agent
- Pareto (ABC) analysisEvery item ranked by its total, with its share, the running share and an A, B or C classSee the workflow Template
- Inventory turnover by SKURank Shopify SKUs by inventory turnover ratio using product, order, and inventory exports from the last 12 months.See the workflow Built by the agent
- Cohort retentionEach month's new customers, and the share still buying 1, 2, 3… months laterSee the workflow Template
- Customer segmentation by revenueSegment Stripe customers into revenue tiers from exported customer, charge, and threshold files, then count customers and revenue in each tier.See the workflow Built by the agent