On Editing Workflow: Cannot Add a Transition because

[rcdpanjaitan]

I'm trying to mark every issues that already deployed state as resolved

So I created a state "resolved" on the workflow.

But somehow, I can not make a transition from Deployment to Resolved. The warning is "you can not perform this on a draft workflow..." Well then how to insert the transition if i'm not on a draft (on editing a workflow)?!

But, the funny thing is, during editing (drafting), I can make a transition from Done to Resolved, no such warning like the previous one. I wonder why.... Please enlight me.

[Nic Brough -Adaptavist- · Accepted solution]

There is a long-standing bug in the draft workdlow editor - it can not add a transition to a step that does not already have at least one outgoing transition.

Atlassian have said they're not going to fix this because it only affects a tiny handful of people (admins who have not seen it before, or have inherited a system from one), and there is a simple fix which is a minor inconvenience for most.

You'll have to copy the workflow, edit the copy (it won't go into draft, so you won't have the problem), add the transition out of the step (while you're there, check for other steps with no outgoing transitions too) and then go to the workflow scheme and swap the old workflow out for the new copy.

[Ismael Jimoh · Accepted solution]

Hi @rcdpanjaitan 

1. Create a copy of the workflow,
2. Add your nee status and transition to it
3. Associate this new workflow with your project.

This has been the only workaround I found for this issue.

Let me know if issue persists or you need further clarification. Also the problem only occurs on default workflow created with your project.

[Angela Trigg (Quarles)]

This is crazy. This interface is confusing enough as it is and then to come across this error and have to do some work-around just because I want to do something basic like add a status and transition?

[Angela Trigg (Quarles)]

Ugh, and now I've done the Copy workaround and assigned that workflow to the correct Issue Type but now all of my existing issues are still using the old one?