When closing Sprint X, I had accidentally moved the remaining issues (24) to a Sprint X+2 rather than the next one needed Sprint X+1
To correct this, I mistakenly did Tools | Bulk Update and edited the Sprint field for all 24 issues to Sprint X+1. However, this has wiped all history of the completed Sprints some of these tickets had been continuously bumped from. This also means Sprint X report is now incorrect.
To correct:
Most were just from Sprint X; for these I did following:
- Bulk Update Sprint field back to Sprint X;
- One by one individually edit Sprint and appended Sprint X+1.
However, I have 9 issues where completed Sprints included more than just Sprint X, eg Sprint X-2, Sprint X-1 etc.
How can I update Sprint field to include more than 1 completed Sprint value?
When doing through Bulk Update, did not allow me to enter more than one value separated by commas, only expecting numeric format.
The reason why i want this is to ensure previous Sprint reports also are correct.
Hi, Rathna
The only is by using the sprint ID separated by commas. The Bulk Edit issues allows you to enter more than one value for the sprint field this way.
If you need help about how to get the ID of your sprints, this thread has some suggestions for that: Get latest Sprint ID
Hope this helps!
Gabi
Atlassian Team
This is not true. Bulk edit does not allow to enter multiple values in Jira Cloud. When using values NN1, NN2, I get an error:
Sprint id must be a number: 766 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Remove the spaces from your comma separated list, and it will be successful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@flushedCrusher This works for me, thank you so much!
I was able to bulk-add multiple sprints to multiple tickets by using the sprint ID in a comma-separated list, without spaces (for example: 100,101,102). This will save me a lot of time in the future if Jira fails to move all issues from one sprint to the next.
I really appreciate your suggestion, thank you again!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online 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.