I recently found this post regarding the topic. This works as long as there is only one Sprint listed in an issue or a story. However, when issues get delayed they often get pushed to a new Sprint. For example:
An issue starts in Sprint 8, but gets delayed. It will now have its Sprints listed as: Sprint 8, Sprint 9.
The automation rule in the URL above will pick Sprint 8 instead of Sprint 9 whenever the Sprint value changes. How can I make sure that it will change the dates according to either the last Sprint in the Sprint list or the currently active Sprint (we only have one Sprint active at a time)?
Hi @Luc Evertzen welcome to the Atlassian Community!
When you completed Sprint 8, did you move the incomplete issues to Sprint 9?
When completing a Sprint there is a dropdown where you can select where to move the Sprints to. I use that feature. I think the problem arises because every issue has its Sprint history listed in the Sprint field, instead of just the Sprint the issue is currently in. It will retain all Sprints it has previously been in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Dave Mathijs Alternatively I would also be happy with the ability to select the last sprint from the array, for example:
{{issue.Sprint.endDate.jiradate}} -> {{issue.Sprint[-1].endDate.jiradate}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira Product Discovery Premium is now available! Get more visibility, control, and support to build products at scale.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.