A previous admin set-up a workflow/schema with a closed status that does not have any outgoing transitions. I need to add a re-open status to the workflow and allow the users to transition the status of an issue from "closed" to "re-open", but the system will not allow me to create the transition - stating "the step 'closed' has no outgoing transitions in the active workflow, so you cannot add any outgoing transitions in the draft workflow."
Is there any way around this? Or is my only alternative to create a new project with the correct schema/transitions and then migrate the existing issues to it?
according to https://confluence.atlassian.com/display/JIRA/Configuring+Workflow this is correct. You cannot do this with an active workflow.
But you don't have to create a new project. Create a copy of your existing workflow, edit it and add it to a new Workflow Scheme. Add this scheme to the existing project. Every issue will be converted to use the new workflow, but this is maybe better than creating a new project.
Just jumping in here Thomas... i have the same problem.
So I have this workflow which is part of 2 Workflow Schemes. Each of these schemes are attached to projects with thousands of historic & current issues/items.
What's the step-by-step process if I wanted to create a transition out of 'Deferred' (to 'Ready for Dev') in this workflow?
1. Create copy
2. Edit Copy (add the transition)
3. Add this 'new' workflow to the 2 schemes?
4. Remove the 'old' workflow from the 2 schemes?
Confused with the last 2 - especially since it'll all explode like a big bang if issues do not stay in their old statuses!
3. Create two new workflow schemes as copies from the old ones
4. Remove the workflows you want to replace with new ones
3. Add the new workflows to the new workflow schemes
4. Replace the old workflow schemes in your projects with the new ones
If the new workflow does not have all the old statuses, you will be asked to which new status you want to convert the issues.
thanks my friend.
actually - what i found to be working better was this..
this saved me from having to 'Switch scheme' in each project that used the old workflow scheme.
That said - wouldnt have got there without your help. Thanks a tonne mate!
Thank you so much for posting this answer. IT WAS SO HELPFUL !!
I wasted about 2 hours before finding this answer.
I really don't like and understand why Atlassian had to make this SO COMPLEX, UNINTUTIVE, AND DIFFICULT TO USE. URGH !!
JIRA is now officially the most difficult tool to use at our disposal.
There is a relatively painless way to fix this (apart from losing the changes already made to the workflow) without reassigning the workflow scheme to every project that uses it.
Follow these steps:
Effectively, this makes the workflow temporarily unused so you can edit it.
I found reference to Atlassian JIRA KB quoting official product documentation section: https://confluence.atlassian.com/jirakb/cannot-add-transitions-or-delete-steps-in-draft-workflows-203392961.html
It would be helpful if someone could explain what this error even means? In my case I had an 'open' state that I removed all the transitions from and pointed them to a 'ready for dev' state instead. Then later I decided to move them back to open, the way they were originally working and moving them back triggered this error. Open had outgoing transitions originally, I moved them and then put them back, and it tells me there are no outgoing transitions? What is it even saying?
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