Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue Removing Bug or Taks from sprint

Steve Vick March 27, 2019

I have a strange workflow issue and I'm not sure where to look. 

If I want to remove an item from a sprint, it wants to automatically move it to another project (not another sprint in same project, just to be clear) and not the backlog. Some workflow appears to be screwed up (I'm new to this environment) and I want to fix it. What should I look at to fix this problem? 

1 answer

0 votes
Jack Brickey
Community Champion
March 27, 2019

How are you removing the issue from the sprint? If you go into the issue and simple edit the Sprint field and clear it that is the first step. Where is shows up next is not driven by the workflow. Now if the issue was originally in the backlog of the same scrum board where you just removed it then certainly it should then show in the backlog again. 

Steve Vick March 27, 2019

Sorry, I should have mentioned that. Manually moving to backlog from sprint or simply editing the ticket and removing the sprint WILL move the item to the backlog. It's only when the user right clicks and selects remove from sprint when I see the problem. I'd really like to fix it.

I'm pretty familiar with Jira but never encountered this before so I am stumped. 


Thanks

Jack Brickey
Community Champion
March 27, 2019

That is interesting. TBH I have never even attempted to do that. I will see if I can test it out on my side and let you know what I find. My expectations should be that it would behave the same and go to the backlog. Now if that issue exists on another sprint/board that would be different. I assume the issues are only associated with a single sprint when you go to remove?

Steve Vick March 28, 2019

No, it only occurs on one board. It's very strange to me too. I'm stumped! And it only occurs on the sprint board. For that same sprint, if I view it while in the backlog issue view and right click, I get the option to move to next sprint, top or bottom of backlog. 

Steve Vick March 29, 2019

Never mind on this issue. I discovered they are not being moved to another project. Instead they are being moved to a sprint that doesn't exist in this project, which means someone screwed something up, perhaps in the DB.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events