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)?
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.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events