You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We would like to be able to identify tickets by the sprint the ticket has been delivered in, as opposed to all the sprints the ticket has been in.
Ideally this would be doable in JQL with something like "LastSprint" or "FixSprint" such as:
LastSprint = 1234
Sprint = LastSprint(1234)
Has anyone had the same need ? and found a solution ?
I'm even considering an extra field and some automation.
PS : Please note that this is not the same thing as openSprints() and closedSprints()...
To do this with an automation rule, and have the results reportable later, you will need a custom field and a rule. You will need to decide what data you want to save for the sprint, such as the name, id, etc. or perhaps a mashup of the sprint attributes.
You can theoretically set this for older, completed sprints' issues, with some assumptions and a more complex rule. (For example, assuming that the most-recent sprint is the "Fixed In Sprint".) I recommend ignoring that rule unless you really need it.
I wouldn't be surprised if this could be done via automation; after all, Jira keeps track of all sprints of an issue, so it's very likely a matter of getting ahold of the latest one. Since I don't have a lot of experience with this myself I'm afraid I have to leave the details to the experts - sorry!
This being said, if you're open to solutions from the Atlassian Marketplace, this would be easy to do - i.e., without any scripting or automation required - with the app that my team is working on, JXL for Jira.
JXL is a full-fledged spreadsheet/table view 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 last sprint (along with several other sprint-related columns).
This is how it looks in action:
As you can see above, you can sort and filter by this column, and also use it across JXL's advanced features such as issue grouping, sum-ups, or conditional formatting. Once you've narrowed down your list of issues, you can work on your issues directly in JXL, trigger various operations in Jira, or export your issues with just one click.
Hope this helps,