Rollover tickets and points per sprint

[Joseph Akbrud]

Hey, all.  Apologies in advance if this is a weird or dumb question, I am new to running "advanced" JIRA queries.

I tried searching for this earlier with no luck.  I am looking for a query that I can run in JIRA to get a list of tickets and an average number of points for stuff that has not been completed in a sprint.

Ex:

How many tickets were rolled over for projects A, B, C, and D over the last 6 sprints.  The ultimate goal is to get an average number of points and tickets per sprint that are rolled over for a given period of time.

Thanks in advance, all.

[Bill Sheboy · Accepted solution]

Hi @Joseph Akbrud  -- Welcome to the Atlassian Community!

I am unclear what problem you are trying to solve with those measures; however, a query like that isn't possible with out-of-the-box Jira Cloud JQL.  The reason is the way the sprint field stores prior values and the lack of a built-in indicator for "rolled-over" and scope changes.  The information is in the history and not easily accessible with JQL.

If you want to do report going forward, you could add some custom fields and use automation for Jira (A4J) to set the fields and help with reporting... Or purchase a marketplace reporting addon.  Or examine the Insights built-in reporting to see how that would help: https://community.atlassian.com/t5/Jira-articles/Introducing-insights-for-Jira-Software-Cloud/ba-p/1746357

If instead this is a one-time/few times need, it may be easier to:

• export the data from the last 6 sprints to a spreadsheet
• use the sprint information and resolved dates to detect the carry-over
• perform your analysis, possibly with scatter and histograms rather than averages to see the patterns
• generalize your spreadsheet to leverage the Atlassian-built Excel or Google Sheets plugins, allowing reuse

Best regards,
Bill

[Joseph Akbrud]

Thank you!  I ended up leveraging the Google Sheets plugin and exporting the data manually.

[Chitrangada Wagh]

I think this is a fair ask and has to be common across all orgs. We shouldn't be moving away from Jira just to get the list of tickets that are rolled over.

[Bill Sheboy]

Hi @Chitrangada Wagh -- Welcome to the Atlassian Community!

The built-in sprint reports support that information (scope change and rolled over items), allowing teams to review it and learn how to improve.  For teams using the Scrum Framework, that can happen every sprint during the retrospective.

A challenge is when teams want to do something outside of reviewing their work for sprints in Scrum, perhaps for management reporting, etc.  For example, rolling up such information across different teams over longer periods of time...things an organization may want to do but are not supported by built-in functions.  That is where data exports to other tools and/or use of Atlassian Marketplace apps can help.

Kind regards,
Bill

[Chitrangada Wagh]

Sorry, my bad. I got it now.

Thank you, Bill.

[Bill Sheboy]

No worries, and I agree there are lots of things to improve in the Atlassian tools. 

I wish there was a reporting engine, like in competitor products, to allow just-in-time report definition and display.  Teams never know what they will need to see as their work methods improve...and so fixed/narrow reporting is not always super helpful.