The project has the default workflow applied to it. I created a new workflow that is currently inactive, thinking I could then apply the new workflow to my project. Is this possible, or do I have to edit the current workflow that is already applied to the project?
Hi David,
no, of course, you can apply your workflow to the project. Do it like that:
This was, of course, a very short description. You can find detailed information here:
https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html
But if you have any further questions, don't hesitate to ask here.
Hey Thomas,
Thanks for the reply. I'm not to the point where I want to make the change just yet, but I wanted to be sure I could. I'll follow your steps once I'm ready.
Thanks again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome, @David Rue
If you think, your question is answered, please mark the answer with the check-sign.
People with similar questions can find answered questions more easy with such a marker.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Thomas Schlegel Is it possible to do same transition without switching no new workflow scheme (i.e. replace current workflow in existing scheme by other workflow)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Eugene Kovalchuk ,
yes, of course. Just replace an existing workflow in an existing scheme with a new one by assigning it to an issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Thomas Schlegel. Thank you for prompt feedback!
One more question. First screen of scheme switching recommends to “backup Jira data before proceeding with the workflow association”. Does replacing a workflow within existing scheme is a transition of same complexity in terms of risks?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, it is always a good idea to have a backup.
Changing the workflow scheme will look at every single issue in your project, assign the workflow to every single issue and replaces the status which do not exist anymore with the new ones (you have to define the replacement rules while changing the scheme).
We never had a problem with that functionality for more than 13 years now, but it is recommended - I think for a good reason.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, thanks for the info. It's very useful to me!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I switch workflows to one I have created in the same scheme will the assigned statuses be lost or will they pick up on the new workflow ? - Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Thomas Schlegel, will changing a workflow within an existing workflow scheme trigger a look at ALL issues within the project with that issue type, or only OPEN issues within the project with that issue type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.