As a JIRA administrator, I have several times edited and updated the workflow that our projects are using.
Today, when trying to edit the workflow and adding new transitions from "backlog" to "open" I'm getting the following error:
You cannot perform this operation on a draft workflow. More Information.
(where "more information" leads to the confluence page of editing workflows)
I don't understand what I'm doing wrong as it is clear that I'm working on a draft workflow that I will need to publish later on.
in your case you're running into a known issue. You can't add outgoing transitions to final statuses.
If you want to work your way around this:
Another thing you can't do on active workflows (drafts) is to delete statuses
When editing a draft worflow, some statuses/steps cannot be deleted and outgoing transitions cannot be added. This makes these steps and statuses useless.
JIRA contains specific code that removes the ability to perform these edits to occur on draft workflows.
A snippet from the workflow documentation:
Limitations when editing an active workflow
Please note that the following limitations apply when editing an active workflow (i.e. a draft workflow):
It is not possible to edit the workflow name (only the description) if a workflow is active.
Workflow steps cannot be deleted.
A step's associated Status cannot be edited.
If a step has no outgoing transitions (Global transitions are not considered), it cannot have any new outgoing transitions added.
A step's Step ID cannot be changed.
There are two different options:
I just ran into the same issue. I was able to create a new status and transition just fine at first. Then I published the draft and decided to go back and edit the workflow again. Now it's telling me I can't add a transition, which is strange since I was able to do it a few minutes earlier. There's got to be an explaination for this.
This is incredibly non-intuitive. I just went through the process of making a new workflow and then moving all of the items over to it. I just copied my original bug workflow and named the new one Original Name (v2).
This really should be much simplier, once a draft is published it should push you through the reassignment process (if needed). I don't know why Jira has to overcomplicate everything so much.
Yep... appearently, and it's over 2 years...
For me it's not worth adding the "Undo review" transition from "Done" to "In review", so we have to live with an out-of-date-workflow.
The workflow is shared by 5 projects, so it will be quite some work to disable the workflow and reeneble it again...
I will show the monetary importance of this bug by using a very simple and real user journey map in the hope that Atlassian better understand the problem and prioritize it higher in their own product roadmap:
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot