Query help. carry over sprint to sprint

[dan_marcantel]

Anyone have a good Jira query that shows what stories are carried over from sprint to sprint.

I have tried old queries with the new company I work with but none work because the way the set it up is so jacked up. 

basically I want to see any story that did not reach a done state in one sprint and carried over to the next sprint. Seems to be quite the problem where i am at now. Poor sprint planning. 

Any good reporting plugins? 

[Jack Brickey · Accepted solution]

i think that you would need an addon e.g. Scriptrunner or similar. With scriptrunner you could use 

issueFunction not in completeInSprint(board name, [sprint name])

but that would only cover a specific sprint. Unsure if there is a way to cover all historical sprints. 

[dan_marcantel]

I'll try it 

[dan_marcantel]

I can't try script runner my company wont let me buy new plugins or even try them.

[George_ Sanju]

This does not work.. It is pathetic that  JIRA cannot provide a report of story carrying over from one sprint to another. Such a shame for a product to provide the simplest of the report

[Stefanie Sullivan]

@Jack Brickey  Is there a way to report on the previous sprint vs specifying a hard coded value?

[Jack Brickey]

Hi @Stefanie Sullivan , is your question related to the topic of this post, I.e. how to report on sprint 'carry over' or are you asking specifically about reporting on closed sprints? The later is available in most default sprint reports where you can select the sprint of interest.

[Stefanie Sullivan]

Hi @Jack Brickey  I am looking to create a dashboard to show which issues keep carrying over and how many times. I would like to see that info for the current sprint and the previous sprint.

[Jack Brickey]

Hi @Stefanie Sullivan , I haven't given this a lot of thought as there hasn't been a need. However, I would play with Automation and a custom number field. Something like this...

for the automation rule...

trigger = sprint completed

condition = for all issues not in done column category

Action = increment the counter

Action = add comment for historical purposes, e.g. "This issue was not completed in xxxx sprint". The xxxx is a smart value for the sprint triggering the rule.

for the custom field ("sprint miss count") default it to "0".

with this you could build filters that could be used with dashboard gadgets - project = abc and sprint is not empty "sprint miss count" != 0

you could use pie charts or two dimensional gadgets, etc. to display.

final note - there certainly could be a better way to achieve your goal. I just wanted to share my quick thoughts. 

[Stefanie Sullivan]

will bring that back to the team and let you know how it goes. thanks!

[Chabba, Sunish]

Tried the following but it showed an error upon saving.

• The rule has been configured with components that require issues to be provided by the trigger. To run these components you must add a branch for this sprint or JQL. The following components require issues: Issue condition, Comment on issue

[Jack Brickey]

Hi @Chabba, Sunish ,

yes the branch will bound your issues to those in the Sprint. Use the following and add your action components.

[Chabba, Sunish]

Thanks @Jack Brickey . 

[Scott Thurston]

I think JIRA should come up with a report that shows all the items that were carried over across multiple sprints. This would help teams identify if they are:

• over-committing at the start of sprints
• if they are beginning in work that is not really ready for development (thus blocks happen and the story does not complete in the sprint).
• If they are sizing stories to low
• poor acceptance criteria
• etc

Reviewing carryover work from a nice report would really help teams conduct good retros and improve. 

[Yolanda Repetto-Logan]

Agree!

[Scott Thurston]

Would it not be super helpful to have an icon or indicator on issues that are carryover.  Make it stand out a bit so it is easier for the team to spot, monitor, track, and helpfully address and improve on.

[Mikel.John]

I was looking for this exact thing and found what might be a simple solution for people. 

1) Write a query of your current sprint.  Really 'Sprint in openSprints()" which will always find you the current open sprint.

2) Make a dashboard or go to your dashboard.

3) Add the Pie chart gadget to the dashboard

4) Select your query

5) Select Statistic Type = Sprint

The pie chart will then give you a break down of all of the Sprints as a piece of the pie.

For example

10 items in Sprint 10

6 items in Sprint 9

3 items in Sprint 8

1 item in Sprint 7

Basically this means, you have 1 item that has been in 4 sprints, 3 items in 3 sprints, 6 items in 2 sprints, and 10 items in your current sprint.