How to track sprint carryover count per issue in Jira Cloud?

[Fabricio Riveros]

Hi everyone,

I’m looking for advice on how to track sprint carryover/rollover in Jira Cloud.

Definition:
By “carryover,” I mean an issue that was included in a sprint, was not completed by the end of that sprint, and was then moved into a later sprint.

What we need:
1. Count how many times each issue has been carried over.
2. Identify issues that have been carried over across multiple sprints.
3. Calculate rollover/carryover percentage per sprint.
4. Show trends across several sprints, ideally by board/team.

Environment:
- Jira Cloud
- Jira Software Scrum boards
- Company-managed projects

Questions:
1. Is there any native Jira Cloud way to report this per issue?
2. Has anyone implemented this using Jira Automation and a custom numeric field?
3. If using Automation, what trigger/condition/action pattern would you recommend?
4. Are there any reporting apps that handle this well using sprint history/change history?
5. Any known limitations with sprint field changes, completed sprint history, or issues moved between boards?

My initial idea is to create a custom field like “Carryover Count” and increment it when an issue is incomplete at sprint closure and gets moved into another sprint, but I’m not sure what the safest automation design would be.

Thanks for any guidance or examples.

[Gabriela]

Hi @Fabricio Riveros, welcome.

Jira has no native per-issue carryover counter. The Sprint Report (Reports → Sprint Report) has an "Issues Not Completed" table per sprint, so you can see what rolled over in a given sprint, but nothing aggregates that across sprints for one issue.

A running count is workable because the Sprint field is multi-valued. It keeps every sprint an issue has been in, so the number of sprints it spans is one more than the times it was carried. Atlassian has a KB for exactly this ("How to track the number of sprints a Jira ticket has moved through") where you add a Number custom field and an automation rule updates it on the Sprint Completion trigger.

For rollover percentages and per-team trends, eazyBI is the usual route; its sprint scope measures go past what native reporting exposes.

Best, Gabriela