Skip to content
Workflow · Track and forecast · Opening soon

Jira sprint report across sprints

Export your Jira sprints and issue sprint history, then load both files into the workflow. It joins sprint data to issue history, totals committed and completed story points, and flags sprints below 70 percent completion.

Early access opens shortly. Check back soon.

Someone typed

“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”

The agent read it as

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.

  1. File
    Jira sprints
    CSV export · 6 rows
  2. File
    Jira issue sprint history
    CSV export · 42 rows
  3. Step
    Make sprint join key (Jira sprints)
    Step 1
  4. Step
    Make sprint join key (Issue history)
    Step 2
  5. Join
    Add issue sprint history
    6 of 6 paired
  6. Step
    Calculate sprint results and carryovers
    Step 4
  7. Result
    Jira Sprint Carryover
    9 rows · 6 flagged
  8. Schedule
    Runs when you say
    Proposed

On the sample files, every step runs and the result has 9 rows.

What you get back

The result of that run, the rows to look at first.

Jira Sprint CarryoverSample data9 rows
4 on target2 below target
Row typeSprintCommitted pointsCarried over pointsCompletion %StatusIssue keyCarryoversStart dateEnd date
SprintSprint 3818338.9Below target··2026-09-212026-10-04
SprintSprint 4017035.3Below target··2026-10-192026-11-01
SprintSprint 3618083.3On target··2026-08-242026-09-06
SprintSprint 3721385.7On target··2026-09-072026-09-20
SprintSprint 3920090On target··2026-10-052026-10-18
SprintSprint 4120090On target··2026-11-022026-11-15
Carried-over issue·····APP-2012··
Carried-over issue·····APP-2022··
Carried-over issue·····APP-2032··
9 rows in the result. Sample data: illustrative figures, not business results.

How it works

How to use the Jira Sprint Carryover workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 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?
Export your Jira sprints and issue sprint history, then load both files into the workflow. It joins sprint data to issue history, totals committed and completed story points, and flags sprints below 70 percent completion. It also lists issues carried over two sprints or more.
What export should you use from Jira?
Use exports that include sprint data and issue sprint history, with story points and sprint membership in the rows. The workflow needs the sprint records and the issue history together so it can compare committed, completed, and carried over work.
What happens to rows that do not match?
Rows that do not match the join key are left out of the matched result for that step. They are still part of the source files, but they do not appear where the workflow needs a linked sprint or issue record.
How do you change the rules?
Change the rule text in the workflow, for example the completion threshold or the carryover condition. You can also rewrite the steps in plain words so the file is grouped, filtered, and flagged the way you want.

Get early access to this workflow

It opens already built and working on sample files. Swap in your own exports to see your result.

Early access opens shortly. Check back soon.

Workflows like this

The number you report every month, rebuilt from the latest export, plus the forecast that follows from it.

All track and forecast workflows →