I am attempting to write a query that can help show me stories that have carried over. In Jira, they are still associated to all of the sprints they have been a part of. So in this example, I have story X that I added to sprint 1. Then that story was not completed and it carried over to sprint 2. And say for whatever reason it then carried over to sprint 3. I want to write a JQL statement that will show me this so I can apply this to a large swath of projects.
I can write this query that returns the result:
status != Closed and sprint = 1
I can also write this query that would return the same result:
status != Closed and sprint = 2
But what i really want is something like this:
status != Closed and NumberOfSprints > 2
But I can't figure out how to do something equivalent to NumberOfSprints.
I have jql that looks to see if an issue is in both a closed sprint and an active sprint
sprint is not EMPTY and sprint in closedSprints() and sprint in openSprints()
You could run this and then combined it with a query that looks for issues in closedSprints() and futureSprints() - this would find any issues moved to a sprint that has not yet started (so it's not "open")
Hello Victor, I really have not found found anything I can do solely in Jira to get these results. One can export the results of a jql query to excel and work with the data from there, but that is a two step process which our end users would not be as comfortable with.
When time permits, I am going to finish a sql query I am working on to find issues that meet this criteria, then try to build a custom jql tag.
I'll update this thread should I get a solution.
I want to do this too so that I can see how frequently 13 point stories are completed in a single sprint. Really what I want to see is the frequency that a story is carried over into another sprint by story point estimate (i.e. 90% of 5 point stories are completed in 1 sprint, 90% of 13 point stories get carried over).
This approach is tedious but it works for stories in more than 1 sprint...
find all of the sprints for your board:
(sprint = 111 AND sprint in (222, 333, 444) OR
sprint = 222 AND sprint in (111, 333, 444) OR
sprint = 333 AND sprint in (111, 222, 444) OR
sprint = 444 AND sprint in (111, 222, 333))
This does not work for me, I cannot find out all the sprint numbers I want to exclude include. I am working on a project were we have created 4 Jira projects one fore each scrum team and we share work. A issue worked by one team and not finished by them can he handed over to another team based on priority.
This is probably contrary to the post (i.e. a way to do this with JQL), but i do reports on this out of excel. Here are the steps:
1. Do an issue search for: project = "Project Name" and status = Done order by key asc
2. Filter using the Colums filter for "Key" and "Sprint" only.
3. Export to Excel, remove the top 3 Rows and Bottom row (junk Jira puts in the export)
4. Save as CSV, open new excel worksheet and import data from Txt, choose the CSV and add Delimeters on Commas. (this will save each sprint label into a new colum for every key)
5. on the last empty column, use the CountA function to count non-blank cells in as many columns as you have sprint data in (i sometimes have up to 5 :( )
The end result is a list of all stories and how many Sprints they touched. You can also add additional fields in step 2 like Assignee if you want to see who has a habit of carrying over stories etc... just make sure the spint field is at the end of the CSV for ease of importing.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs