Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Cancelled issues dragged on from sprint to sprint

We cancel an issue and then close the sprint. The issue keeps marching on from sprint to sprint endlessly until somebody notices it (cancelled issues are not visible in any of the normal views). How can we stop this from happening? Cancelled issues should not carry forward as "unfinished work" when closing a sprint. 

1 answer

1 accepted

1 vote
Answer accepted
Jack Community Leader Feb 26, 2019

you need to make sure "cancelled" equates to Done in Jira scrum terms. Preferably "Cancelled" should be a "Resolution" value when marking an item as Done and "Done" should be the final status and in the right-most column of your scrum board. By doing this Jira sees these issues as done w/in the sprint and therefore will not put them back into the Backlog when closing the sprint. Now, if your current workflow has "Cancelled" as an independent status then you need to ensure that status is mapped to the right-most column on your board just as "Done" is.

I can try this. I had thought it only affected cancelled items but there are 5 unused statuses in the unmapped section. I'll keep a closer eye on it with this in mind to see if the problem affects all 5 of those statuses. 

Jack Community Leader Mar 01, 2019

@Liz_Pat , i'm trying to follow you here. Any unmapped status simply means that if any issue in the project(s) associated w/ the board are transitioned to any of the unmapped statuses then they will not be shown on the board. Of course the issue are still there they simply are not shown on the board because the board has them "filtered out". You original question is about how to treat "Cancelled" issues as "Done" as far as them not being carried forward from sprint to sprint. In short - any issues that you do not want to move back to the backlog/future sprint must have a status that is mapped to the right-most column on your scrum board.

Like Tony Vlcek likes this

The point is very clear. Thanks for the reply. I will continue to monitor. I'll close this issue since my guess is there is something else going on too. Our system has a lot of inconsistencies and it's tough to disentangle them enough for me to troubleshoot. Thanks for the tips. 

Hello team

 

I planified my sprint v01.

In this sprint i have one issue that it's cancelled (status = cancelled).

I do not see more my issue in my sprint , it's removed from sprint i can not find it in the baklog .

 

Note if i reopen my sprint i can find my issue .

 

 

Regards 

This doesn't make sense... In my right most column I already have the "Done" status mapped. If I also map the "Cancelled" status there it means there is no proper visual differentiation when actually dragging items meaning that team members start to cancel instead of complete issues....

Jack Community Leader Jul 01, 2021

In CMP and traditional boards if you have multiple statuses mapped to a single column then when you drag an issue into the column you will see dotted lined boxes for each status and you can drop them into the appropriate one

Well my teammembers don't haha. And after it's been dragged there's not visual indicator anymore. 

I'm now trying to just filter cancelled out of the board entirely and see if I can complete the sprint monday even though there are cancelled issues linked to the sprint (but not filtered on the board) that are not in the "rightmost column". 

Jack Community Leader Jul 01, 2021

Couple thoughts….

  • include Status on card layout
  • consider not having multiple done category statuses. Rather use the resolution to indicate cancelled. This is what I do most of the time. 

Changing card layout is smart, never used the feature.

I'm using resolution of "Done" when "Cancelled", but you don't mean that I think...

Jack Community Leader Jul 01, 2021

No I mean use Done as your only done category status and leverage Resolution for the variants of Done: done, cancelled, won’t do, cannot reproduce, etc.

while there are scenarios where I use more than one done category status they are rare. 

Oh right, already had it set to "Won't do" resolution. However this still blocks sprints from being closed...

Extremely frustrating, I'm now blocked again from closing the sprint because there is a task that has a subtask which has cancelled state :/

 

close sprint.pngMVP-479.pngmvp-505.png

Jack Community Leader Jul 05, 2021

Is “cancelled” status in right-most column? 

That was the thing I wanted to avoid as teammates accidentally drag the issues in the Cancelled column. ;)

But I'll go for editing the Card layout to better illustrate actual status.

Jack Community Leader Jul 05, 2021

Agreed that is why I almost always opt for a single done status and allow the resolution to specify the type of done i.e. it can be done-canceled. In this way they can drag the issue to the done column and the pop-up will require them to specify the resolution.

But I'm using my Done status to set resolution to "Done" and my Cancelled status to set resolution to "Won't do".

However "Won't do" isn't considered "Done" (resolution/status) and I can't set "Won't do" and "Done" simultaneously as resolution right?

Jack Community Leader Jul 07, 2021

Let me reiterate- My suggestion is to get rid of the canceled status altogether and replace it with status done and a resolution of canceled in this way all completed issues will have a status of done and the resolution of those issues will vary depending how/why it is considered done.

if you want to maintain cancelled as a status then that is fine BUT you must put that status in the rightmost column to have those issues completed as part of the sprint. I simply prefer the other solution.

Like Robert YK likes this

Ahhh i can do two transitions to "Done" obviously :)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

736 views 2 21
Read article

Community Events

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

Events near you