Issues with transitioning when using other "Done" status type

[Sarah Fajerberg]

I have a few issues with my workflow. We have added a new status type for "Done" called "Obsolete", but we have some issues with it. I have checked and the "Obsolete" type should have the same properties as "Done". 

So one example is, when one sub task in a parent issue is moved to "Obsolete", the parent issue is not allowed to be moved to "Done", even if all other sub tasks are "Done". 

What can be done about this? Is there something in the workflow that I'm missing?

[Rilwan Ahmed]

Hi @Sarah Fajerberg ,

Welcome to the community !!

Do you have a transition to "Obsolete" status in your parent ticket type workflow ? 
Do you have any conditions in the "Obsolete" transition ? 

Is there any error shown while transitioning ticket to the "Obsolete" status ?

Please share screenshots of your ticket status dropdowns, Parent ticket workflow and the transitions conditions. This will help us to pin down on the issue, 

[Sid Pathirana]

Hi - are the subtasks actually "resolved"?

When your tickets are moved to the new "Obsolete" status, is the Resolution field also being set on those tickets (eg. manually via a transition screen in the workflow, or automatically via a postfunction in the workflow)?