Is there a way to track reasons why tickets roll over from one sprint to the next?

[Holly Roseberry]

We have had many tickets roll over lately and want to identify problem areas (such as underestimated tickets, blockers outside the team's control, shifting priorities, scope creep, resource constraints).

One proposed solution:

When a ticket rolls over, an automation rule would send a message to everyone on the ticket (reporter, owner, etc.) requesting them to choose a reason(s) why the specific ticket rolled over, allowing us to identify any trends.

1. Would this be practical?

2. Is there a better way, such as through retrospectives (or a combination of reports and retros, for instance)?

Thank you for your insight.

[Alexey Pavlenko _App Developer_]

Hi @Holly Roseberry ,

I developed the app specifically for that - Multi-team Scrum Metrics & Retrospective. The app will let you rethink retrospectives in general and offer many additional features.

Please see this article about the approach.

Best regards,
Alexey

[Mathew Lederman]

@Holly Roseberry can you help us understand what you mean by ticket "roll over"? That's not a term I've heard before with respect to Jira tickets.

[Holly Roseberry]

When a ticket rolls over from one sprint to the next, when a ticket is not finished in the sprint.