nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I close a sprint with some subtasks that are "Removed"?

Hugh Guynn

I'm using Jira Cloud. All my issue types, including sub-tasks, have a "Removed" state. Jira by default knows not to show Removed sub-tasks on the board. But it won't let me complete the sprint because those sub-tasks are not completed. My understanding is "best practices" are to set issues to Removed, not delete them. So how do I complete the sprint?

Accepted answers

All comments

Nic Brough -Adaptavist-

Reconfigure your board - add the "removed" status into the "done" column.

Hugh Guynn

That did it. Thanks!

Hugh Guynn

OK... Yes, this did solve the problem as stated. Unfortunately it had undesirable side effects. People would accidentally drop issues onto the "Removed" box in the Done column and the issue would disappear since we filter out Removed issues. And the "Move to Done" option moved issues to the Done column, but Removed status (so they disappear).

Any other ideas?

Nic Brough -Adaptavist-

Not really, you need to consider that right hand column as the definition of done. You shouldn't be filtering it on the board, that gives you broken stats.

Where are you seeing the "move to done" option though?

Jack Brickey

@Hugh Guynn, I wanted to add to what Nic has provided here.

There is one other option to consider and IMO, based upon all i have read above is the best option. Have "Removed" be a resolution and stick with DONE. The use case for why removed exists is well aligned w/ Resolution as it indicates why you are marking the issue done - 'we determined this was an unnecessary task'. This is similar to other resolutions: Done, Won't do, Duplicate, etc.

To your question about the magic of the right-most column, there is no magic but rather how the Jira scrum boards have been designed to work. Could it be implemented differently, sure and you can certainly open a suggestion w/ Atlassian to do so if you wish but I wouldn't think it is likely to be implemented anytime soon if ever.

FWIW, giving other delete privileges is a bad idea. As an admin you could always delete at Sprint closure.

Hugh Guynn

Thanks for the advice - I definitely do appreciate it. After getting a little more experience I might see if I can get a script that automatically deletes Removed sub-tasks when the parent issue is moved to Done. Right now I will take your advice and manually delete them at the end of the sprint.

Hugh Guynn

I think the answer is no, but are you saying in the first paragraph that if I make Removed a resolution (currently it isn't) then I negate the need to have Removed associated with the Done column?

Jack Brickey

yes. just get rid of the removed Status and simply add "removed" as a resolution value or just use an existing one e.g. "Won't do". IMO having the extra status of REMOVED is flawed but that is an opinion of course. :-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

sprint

sub-task