Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can we show issue count rolling over Sprint to Sprint?

Some issues unfortunately rollover from one Sprint to the next. 

Is there a way in JQL to feed a metric showing how many carry over? Not entirely sure yet how to do this, but metrics like these would help our 'New to Agile' team see where they're having challenges.

A metric like:
1) Issue count in current Sprint also found in previous Sprint
2) Number of Sprints that issues have been in   

We have a custom 'Sprint' field so there should be data historically to calculate, right? 


1 answer

1 accepted

1 vote
Answer accepted

Hi @Bud Herz 

You could do this with the sprint report, and/or some JQL to get the various numbers, and/or show those as saved filters on a dashboard, and/or use an automation rule triggered on sprint completed to send a report.

Some example queries would be:

  • Issues in the current sprint and prior sprints: 
project = myProject
AND sprint IN openSprints()
AND sprint IN closedSprints()
  • Issues only in this sprint and no others:
project = myProject
AND sprint IN openSprints()
AND sprint NOT IN closedSprints()

What does your custom sprint field represent?

Best regards,


Bill you're answering another one of my questions?! Good to hear from you again. 
I will try those out and see. Thanks, much appreciated. 

The custom field is always the Sprint name. We use it to sometimes identify one-off Sprints (for patch work, etc) and to standardize it, the normal Sprint name if a regular one. 

Those worked perfectly! Thank you.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

315 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you