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

Can't add transition from Closed status to Reopen Status ... Jira Cloud

Neda Sayan

things were much easier in Jira server ...

I added a Reopen status, to allow open a jira ticket. Now I try to add transition from closed to Reopen it wont let me .. it say, "you cannot perform this operation on a draft workflow...

I can add transition from any other status to Reopen, no error, just closed one gives me this error!

Accepted answers

Fabio Racobaldo _Catworkx_

Hi @Neda Sayan ,

this bug (https://jira.atlassian.com/browse/JRACLOUD-68734) seems to persist.

As workaround, required to add status/transitions to a default workflow (since modifying the default workflow is not possible due to it being active upon project setup) you should :

navigate to workflows
duplicate the current workflow
change the name of the duplicated workflow (but you can't use the active workflow name and can't change the active workflow name, so you are forced to use something entirely different)
add the status/transition
navigate to the workflow scheme
change the workflow in the scheme
navigate back to workflows
delete the default workflow

Hope this helps,

Fabio

Ciarán Ó Néill

What a horrible change!!! I essentially cannot add or delete transitions from an active workflow anymore without jumping through a ridiculous number of hoops... I thought Atlassian understood agile, but this is "first time right or die". Even disregarding agile completely, who thought it was good idea to make workflows immutable? Any workflow that is long-lived should incur changes, otherwise no-one is thinking. I am thoroughly annoyed!!

All comments

Fabio Racobaldo _Catworkx_

Hi @Neda Sayan ,

this bug (https://jira.atlassian.com/browse/JRACLOUD-68734) seems to persist.

As workaround, required to add status/transitions to a default workflow (since modifying the default workflow is not possible due to it being active upon project setup) you should :

navigate to workflows
duplicate the current workflow
change the name of the duplicated workflow (but you can't use the active workflow name and can't change the active workflow name, so you are forced to use something entirely different)
add the status/transition
navigate to the workflow scheme
change the workflow in the scheme
navigate back to workflows
delete the default workflow