workflows

RentalHost November 25, 2015

This question is in reference to Atlassian Documentation: Administering JIRA Software

workflow scheme per project.   I had an existing workflow (Process...) and then I created a new project and started editing the workflow within that project.  The first project then automatically got switched over to that.  Is there any way to get the old workflow back?  I don't see how to assign a new workflow to the new project.  Just a navigation thing I guess, but I'm missing it somehow.  I need two separate workflows for my two projects.

2 answers

0 votes
Dennis Poort November 25, 2015

When you go to the Administration page of your project you can select a different workflow scheme for your other project. So first create the workflow scheme and workflow you require, then go to your project administration page and switch your workflow scheme.

You may need to re-map issue statusses. This step will be asked when switching, so just follow the directions.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 25, 2015

Yes, that's what workflow schemes are for - to allow you to define what workflows are used for an issue type in separate projects.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 25, 2015

Ah, right, the question was edited to provide actual content. Workflows do not get mapped to projects. Projects have a "workflow *scheme*". This scheme tells the project which workflow to use for each issue type in the project It's quite common to have a single workflow for all the issue types, and that's the default when new schemes are created. But it is *very* useful to do be able to do things like "use a task tracking process for all top level issues, but have a different one for bugs because we want to include testing, and have a third really simple open/closed one for sub-tasks. Hence the need for the workflow scheme to define t. So, as Dennis says, create your new workflow. But then you need to create a new workflow *scheme* and tell that to use your new workflow. Then you associate the new *scheme* with the project (and again as Dennis says, JIRA may ask you to re-map status for existing issues)

Dennis Poort November 25, 2015

Indeed workflow scheme per project, ofcourse. Edited my reploy for more clear answer.

Suggest an answer

Log in or Sign up to answer