I create some dashboards to show in which sprint a ticket has been completed.
The problem is that, when a ticket pass from a sprint to another, the value "Sprint" is populated with all the sprints, and in my dashboard it appears several times.
How can I avoid this?
I modified my dashboards to take the value "LastSprint", and I create an automation that automatically updates the value LastSprint when a ticket is transitioned to Done. But the value "Last Sprint" is still filled with all the sprints that the ticket passed by.
I tried to modify the last "edit issue" from to openSprints (), to check if it will work.
Hi @alessandro.romolo.e -- Welcome to the Atlassian Community!
As you observed, the Sprint field is a list of values, helping to preserve the history of what happened to the issue.
You may use smart value, list filtering to get the name of the "active" sprint for the issue using this expression:
{{#issue.sprint}}{{#if(equals(state,"active"))}}{{name}}{{/}}{{/}}
To learn more about this type of filtering, please see this article: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
welcome to the community!
I'm glad you were able to resolve this using Automation! Just for future reference, if you don't want this to eat into your Automation budget:
If you're open to solutions from the Atlassian Marketplace, this would also be easy to do with the app that my team is 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 long list of so-called smart columns that aren’t natively available, including the last sprint, along with many other sprint-related columns.
This is how it looks in action:
As you can see above, you can easily sort and filter by the last sprint, and 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.
This all just works - there's no scripting or automation whatsoever required.
Any questions just let me know,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.