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; } } }

Ticket considered as open by Jira depot of status "obsolete" and resolution set to "won't do"

unknown

Hi,

the title should say most of it. We have a status "obsolete" for subtasks we decide not to do. With the transition there is a post function that sets the resolution to "won't do" (we tried different values here).

Bildschirmfoto 2021-01-27 um 09.09.08.png Bildschirmfoto 2021-01-27 um 11.45.29.png

However we can't close the sprint as we get the message that there are open subtasks. All other subtasks are set to "closed" and I can close the sprint once I change the status to close or delete the subtasks.

Bildschirmfoto 2021-01-27 um 09.09.18.png

From my understanding setting the resolution field will mark the ticket es done. What other factors come into play here?

Many thanks

Accepted answers

KAGITHALA BABU ANVESH_z1zl10

Hello @[deleted],

is the status of MPT-3525 is obsolete ?

Does the obsolete workflow status is mapped under "Done" column on board.

Jack Brickey

you must ensure Obsolete status is in the far right done column of your board.

All comments

KAGITHALA BABU ANVESH_z1zl10

Hello @[deleted],

is the status of MPT-3525 is obsolete ?

Does the obsolete workflow status is mapped under "Done" column on board.

unknown

Hi @KAGITHALA BABU ANVESH The status of MPT-3525 is done.
It has multiple subtasks, all done but one which was "obsolete".

Obsolete was not mapped to the done column as this caused the done column to spit between "done" and "obsolete" when moving a ticket and multiple tickets were incorrectly dropped into the obsolete field. So we decided to make this transition only possible from within the ticket.

Jack Brickey

you must ensure Obsolete status is in the far right done column of your board.

KAGITHALA BABU ANVESH_z1zl10

Hi @[deleted],

As Jack suggested "you must ensure Obsolete status is in the far right done column of your board."

On that case only , sprint treat the issue as closed. to end the sprint

Thanks

unknown

Thanks! That wasn't obvious, in most of the articles the resolution field is mentioned as the master-entity for deciding if a ticket was done or not.

I will mark Jack's reply as the correct one as it's shorter but thanks for pointing it out to me, too.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud