JIRA, you're killing me!
While trying to add transitions to workflows, I keep getting error messages like:
"You cannot perform this operation on a draft workflow." (while trying to add a new transition)
"You are editing a draft workflow. The step "[stepname]" has no outgoing transitions in the Active workflow, so you cannot add any outgoing transitions in the Draft workflow." (while trying to publish a draft workflow - and adding an outgoing transition is PRECISELY what I was trying to do!)
This makes no sense. It's like it's asking me to change an ACTIVE workflow, which I can only do while in DRAFT, then it fails. I can't see any way around this. Is this a bug? If so, when can a fix be expected??
There's a long-standing howling bug in the workflow editor in that it can only add a transition to steps that already have outgoing transitions.
We've been waiting for a fix since the workflow editor got "draft" mode, and I'm afraid it seems to be a very low priority for Atlassian. So there's no fix forthcoming any time soon, and we can't plan on one being released ever.
I'm afraid you will need to work on a copy and migrate.
This popped up for me when a user placed an Issue in our new specified "Done" status. So I thought to be smart and edit the workflow with a Transition to the start of the workflow, but this of course didn't work and gave the aformentioned error. This bug is very annoying and unfriendly towards new users, especially when I have to browse forum after forum to find out other people have the same issue as I have.
Yup, this very error happened to me when I tried to add a new transition to a default diagram where all states are like
[ State ] <--- [ All ]
I had to make a copy of that diagram, make the changes and do a migration. That's why I found this thread and why I replied in a first place.
So could there be any other reason for the error occuring to me? Because if not, this error can affect more than _small handful_ of users, right?
Nope, no other reason. It's a design flaw.
It only affects administrators, and only those who have inherited poorly designed workflows built by inexperienced admins. That's probably less than a "small handful" of users to be honest, or at least should be, as the biggest mistake people make with Jira is "too many admins".
'Poorly Designed' workflow editor... or workflow
Our workflow as designed to allow teams to create their own workflows using 'drop and drag' on their Agile board. Every status only has an inbound 'All' transition. No mention anywhere of this restriction/bug until its too late.
Ie - some teams want to work only with 'ToDo' and 'Done' then they can. And the same flexibility for teams that want to work with a waterfall like SDLC, and they can do that without needing any assistance from a JIRA admin
So how can I fix this without releasing a new workflow that will touch 400k issues and throw our dev stats into the can?
Its bit of a bind (or other words that begin with 'b') to hit this obstacle as we have painted ourselves into a corner with our management reporting that is based on last update date... doh!
Any idea if this has been fixed in newer versions (7.13 or 8) of JIRA?
Anyway, with your excellent ScriptRunner, we were able to come up with an even better solution to create a 'Corrections Needed' scripted field that could be used in a condition on the existing transitions.
So when I develop a workflow I need to know every reversion state ahead of time? I allowed many states to transition to Done, via a cancel transition. The we realized that Canceled needed to revert back to the previous state, but ONLY the previous state and only under certain conditions. Discovering this is not POOR design, its discovery process ex post facto.
I think you have misunderstood the community. The overwhelming majority of the community are people who work with Atlassian software. But we're not Atlassians.
There are, of course, Atlassians here, but I don't know if any of the Jira developers (or, more importantly, Product Owners) are particularly active.
The the moderators/community leaders are not developing Jira, we're working with it. And trying to explain why it is like it is, and trying to help people deal with flaws like this one.
Our moderators and community leaders spend time trying to help. Not fixing code problems, because we can't - we're not buildng it.
You cannot edit the workflow because it is "Active", means it is already assigned to a Project.
(even if workflow is Active you can make little changes, like renaming Status/Transition)
Here is the Solution (it worked for me every time)
- Go to Edit the workflow
- Try to publish (without change) and Create a backup copy there
- Go to JIRA Settings -> Issues -> Workflows
- Go to Inactive Workflow section and try to Edit the workflow that you just created as a backup
- Make the changes and keep the window as it is (you may not find the option to save anything there)
- In a separate window, go to Project Settings -> Workflows
- Go to Add Workflow and select the same Workflow that you just edited in separate window
- Click few Next buttons, if there is no new Status it will probably not ask to match the status between Old and new workflows
- Publish it and your are Done (Close the other window where you still opened that Workflow in Edit mode)
Hopefully it will work for you.
To Atlassian: If you are not going to fix this right away, at least, please make that message clear, admit that this is currently a bug and point to a clearly written step to get around it - like editing it in disabled mode. The lengthy information on the page that you point to really isn't very helpful either. We need good user experience, we all know things will have bugs especially this is a coding tool anyway, so no coverups, be transparent and be helpful.
Not an answer but a comment:
I'm in the evaluation process for Atlassian products and encountered this issue.
This is definitely a big -, not only as a serious flaw but also the response that a workaround is available is too lazy. The feedback on the error is also terrible:
It took me way too long before even considering that something so trivial could be a bug that needs a workaround.
Overall I'm still impressed with Jira, and competing products have their own bugs, so this won't be the dealbreaker, just a considerable negative point.
Come on, just replacing an old test tool that were not covering our needs and fell over this shitty problem. Dont have time to bother with work arounds, all resolved issues will have done resolution set automatically by use of post function until you fix this.
Except from that this tool seems awesome!
This is annoying.
What I've done is start to use Workflow Schemes at project levels, even if they're all just joining to one "Standard Workflow" scheme that points to a single "Standard Workflow" workflow.
That way if i need to make a new copy of "standard workflow(3)" so i can tinker with transitions, I can change it at the scheme level and update all projects simultaneously.
This is just silly. And everyone saying "this is awesome!" for a solution to clone a workflow in order to achieve this basic functionality should rethink what they wrote. "This" is not awesome, any "workaround" sucks. We should just be able to edit it right inside the draft and that's it.
I know, it annoys me too, it's a silly flaw.
There's a longer thread somewhere else on the same subject, with an explanation from an Atlassian which is a bit sketchy about how the mistake was made, but a lot of detail about why it's not going to be fixed.
We got our deliverables regardless of what Atlassian dictates. The awesome part is that with the help of others, we got out of this bind. We did not have to waste as much time and got it fixed, and we can move on.
Awefulness is that JIRA is a product to help us do the dev workflow thing. That's the core of it, and that very core of it does not work, and nothing is being done or taking super long time. The company that promotes Agile is not moving in that agile direction...
@Nic Brough _Adaptavist_As a Community Leader, can you provide a link to the "Official" long description on why this is not going to be fixed? Is there an "Official" thread on this issue?
I ask because in the community there seems to be a lot of "that's the way it is , deal with it," or "if you had experienced and well trained Workflow developers this wouldn't be an issue" comments made by people that are in the know and these seem very condescending to those of us that have to work with this product every day without dedicated staff that knows all of these work-arounds.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events