JIRA: Removing old sprints from migrated ticket to resolve a velocity chart issue
Ran into an interesting problem in JIRA that I managed to solve this morning. Figured it might help out others, so here goes!

It turns out that if you had a ticket that was part of a Sprint in one Project, but then either move it to another project or clone it, it'll still retain a history of the prior closed sprints it was in. At first, that doesn't seem like a big deal, but it means that the Project it's now part of will have messed up Velocity Charts, because it'll start including the Sprints from the other Project. And there's no obvious way to remove the old Sprints from the ticket (editing the ticket only lets you change the current Sprint assignment, not clear out prior ones.) No good!

Fortunately, the Bulk Edit feature provides a workaround and will let you clear out the old Sprint associations, which will then fix the Velocity Charts. And here's how to do it:
  1. Run a search that'll return the ticket you need to remove the sprints from.
  2. Choose the "Bulk Change" option from the "three-dot menu" in the upper right.
  3. Check only the ticket you want to change. Hit Next button.
  4. Choose "Edit Issues". Hit Next button.
  5. Check the "Change Sprint" option. Leave it blank. Hit Next button.
  6. Review the Confirmation screen. Hit Confirm button.
  7. Hit Acknowledge button when the progress meter is done.

For reference:
4
LVL 7

Author Comment

by:Brian Matis
One word of caution: be careful when doing this! Bulk Change is quite powerful and if you're not watching out, you could accidentally change a lot more than what you really want to. I imagine this is why Bulk Change has so many steps to it... Sometimes I'm glad when a task is a bit difficult and cumbersome to do :-)
0

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month