This issue is still dumb

This is a feature, but more specifically it's a MISSING feature.

If I can duplicate a workflow, add the outgoing transition, and then replace the active workflow with the new workflow, clearly Jira is internally handling whatever resolution state concerns there are.  There's no reason the same migration logic couldn't be implemented when publishing a draft workflow.

Short of this obvious solution, there are two other changes Jira could make to mitigate this flaw:

1. As others have already noted, do not allow users to create outgoing transitions on statuses that lack them when editing draft workflows.  This avoids wasted time and effort, but does not really help the user understand why they can't do what should be straightforward.
2. Since the user is going to have to copy the workflow, Jira could at least make it straightforward to do so.  Currently the ability to copy workflows is hidden away in Jira's global settings, but most users are going to approach this problem via a particular project's workflows page.  Why not offer a link to duplicate the workflow at the same time that you show the error message to the user?  Or at the very least, add a Copy Workflow link to the Project Workflows page, either as an Actions icon, or as a dropdown option on the Add Workflow button?

I'm in the SAME situation - cannot add transitions from "Done" to any other state.

Why is this issue closed?  This is a bug, not a feature.  How can this still be a problem after nearly a DECADE?!?

I just discovered that I screwed up by adding a workflow state with no outgoing transitions and now it's apparently going to cost me an hour or two to fix that.  Thanks, Atlassian.

This is not flippin "Closed" – This is still a Bug, from 2008?!!?!!!!!!!!!!!!!!!?!!1?!/1 FLIPS TABLE

I tried the workflow migration, it failed, still troubleshooting, but anyway I am now stuck with these JIRA that is unable to transition out.

This is a silly "feature", JIRA admins are responsible not to break workflow, not Atlassian... now look at how many complains we got

Greetings –

Here's a logic way of getting into this situation

• create project 'foo' with copy of 'simple workflow'
• edit final state of workflow to be 'done'
• assign workflow to project, etc
• realize that the created vs resolved widget doesn't play well with "Done" – only "Resolved"
• try changing "Done" to "Resolved" in custom workflow
• see no option to delete "Done" and force a bulk change
• try deleting all transitions to un-grey-out the "delete" button for "done"
• realize no bulk change options are available to state since there are now no "transitions" from "done"
• **UNABLE* to add new transitions to draft to be able to batch-transform issues from "Done" to anything else

Can you please watch & vote on JRA-19091? Many thanks, Rosie

Atlassian, you should really answer us why you need that closed state and why you consider this fixed. It's certainly not fixed! Please listen to your users andreask

Surely it should be technically possible to reassign the 'completed' status to a different/new step,
...and then allowing the user to add additional transistions to the desired step.

Dear JIRA guys, how on earth can you call this FIXED?
Or can you not REOPEN this ticket due to some silly osworkflow constraint?