Sprint Spillovers - without using Sprint report

[Sarthak Solutions]

Is there way to view sprint spillovers without referring to Sprint report ? I am trying to generate an automated Sprint report Dashboard/View which needs this important information to reflect.

[Bill Sheboy]

Hi @Sarthak Solutions -- Welcome to the Atlassian Community!

In my experience...

Work item carry-over from one sprint to the next is a symptom of some root cause.  Those could include challenges with backlog refinement, sprint planning, team focus, product / code quality, people-incentive policies, etc.  Hopefully, such carry-over is infrequent.  Rather than building reporting for this, I recommend using the existing Sprint Report and discussing this with the team in a Retrospective to identify the root cause, and then design experiments to improve team processes to eliminate the problem.  If carry-over reporting is created without the team discussion, this could lead to normalizing carry-over, or other unintended consequences, reducing the chance the root cause will be addressed.

If the team decides they still want to build automated reporting to track carry-over, they could:

• Investigate marketplace apps / addons to do this
• Use automation rules to detect the condition, adding indicators to the impacted issues.  Then with the built-in features of JQL, report on the issues in the List View or in a Dashboard gadget.

Kind regards,
Bill