Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JQL Show stories that have been moved from the last sprint to the current sprint

Kai Zimmermann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2024

I would like to display stories that were transferred from the last sprint to the current sprint (spillover from the last sprint).

These should be displayed in a reporting section in Confluence and I want to prevent me from having to do this manually for each sprint.  A suitable JQL filter would be helpful here ;)

My only idea so far is that we use "Spillover" as a label to display this. However, I'm not entirely happy with it.

2 answers

0 votes
Hannes Obweger - JXL for Jira
Atlassian Partner
February 28, 2024

Hi @Kai Zimmermann

welcome to the community!

If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart columns that aren’t natively available, including the number of sprints, the latest sprint, and many others. 

With these, you can build a view like e.g. this in just a couple of clicks:

number-of-sprints-v3.gif

As you can see above, you can easily sort and filter by the number of sprints. You can also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

While JXL is first and foremost a Jira app, JXL sheets can easily be embedded into Confluence pages, e.g. using the Confluence HTML macro.

Any questions just let me know,

Best,

Hannes 

0 votes
Clark Everson
Community Champion
January 24, 2024

Hi Kal,

Welcome to community!

Your idea is a pretty good one! Combine that with automation and you could continuously improve it to meet your needs

Unfortunately the changed operator of JQL doesn't support the sprint field, so the way you are doing it is a good starting point

Depending on the metrics you are looking for you maybe able to utilize the label with something like "AND Status != Done"

But within JQL the most you will really get is using the label and going off of status. You could modify the label to also have the date attached for each sprint but that would be a bit manual, though it would improve data.

There are third party database connections such as tableau that could potentially get the data from the database

Best,

Clark

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events