Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x

JIRA

128

Solutions

269

Contributors

Developed by Atlassian, Inc., JIRA is a software tool for issue tracking and project management.

Share tech news, updates, or what's on your mind.

Sign up to Post

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
When ransomware hits your clients, what do you do?
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

2
loading...Arghh!! I really hate it when I write up a bug ticket in JIRA capture and then when I go to submit the bug, I get stuck at a loading wheel and the ticket never generates... Now it looks like I have to re-write the bug... And it wasn't an easy one to describe anyway... Lame.

#rant
0
 
LVL 17

Expert Comment

by:Kyle Santos
(sadpanda)
1
 
LVL 7

Author Comment

by:Brian Matis
Huh... In ranting about this, I think I may have figured out what caused it and how to avoid it... Seems like I closed the original tab that I was getting a screenshot of and JIRA capture doesn't like it when that happens. Didn't seem like that should affect anything (since JIRA capture opens up a new tab for doing annotations of the screen and adding the bug details). But when I ran some quick experiments, I discovered that closing the original tab will definitely trigger the infinite loading wheel when trying to submit the bug in the other tab. When I kept the tab open, could file the ticket as expected... Should probably run a few more validation tests, but it sure will be nice if I can eliminate one cause of this!
1
Well this is interesting... Atlassian (makers of JIRA) just purchased Trello. I use JIRA for work and Trello for personal things, so I'm really curious about how this will play out.

https://techcrunch.com/2017/01/09/atlassian-acquires-trello/
0

JIRA

128

Solutions

269

Contributors

Developed by Atlassian, Inc., JIRA is a software tool for issue tracking and project management.

Top Experts In
JIRA
<
Monthly
>