Hmm, if the message that it is a draft appears, then it would mean that it is an active workflow. This is is basically a failsafe mechanism, to avoid the saving of any accidental changes on an active workflow.
In any case, once you have finished editing, there should be an option to publish the draft. This will make the changes that you have done on the workflow to fully take effect (as it will replace the active workflow). When doing so, you will be given an option to create a backup of the workflow (like I said, failsafe), it's up to you whether you want to keep a copy or not.
Atlassian had made several improvement how you modify existing workflow in the next several releases so the method depends on the version of JIRA that you are using. So please provide this information and I or someone else will be able to assist you. In the older versions 5.0 or earlier the only way was to copy the existing workflow edit the copy and then assisgh the new workflow to the workflow scheme, etc..
If you're seeing the option to "draft" a workflow, then the basic ideas have not changed since that was introduced (the editor has changed a lot, but the principles have not).
To modify an existing workflow, you click "edit", make the changes, then click "publish". That's it. See https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-editingEditingaworkflow(if you're struggling with that, tell us which bit)
Thanks everyone for responding. I have Jira version 6.2. It is only the web version. So, I copy the workflow I want to modify and then I make my changes attach it to a scheme? Once I attach it to a scheme, can I then apply it to my Test Project to see if it works? Also, if you messed up how would you reapply the 'old' workflow?
I think there shouldn't be a need to copy it first (unless it's the default workflow, or if you would like to keep things safe). If you do desire to first copy the workflow, then you would have to indeed :
If the new workflow doesn't work as you expect, then you can just configure your project to use back the previous scheme (the one where it is still using the original workflow).
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
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