Bulk updating workflow changes.

Question

As part of a change we have made, we have split a very complicated workflow into two areas.

Development  (story issue types )and Testing (New issue type)

We now need to associate these two new workflows to our production instance, is there any way to achieve this without having to go into each story type and change it manually?

Rilwan Ahmed · Accepted Answer

Hi @Siobhan Wallace ,

Welcome to the community !!

If you just added two new Issue types (Development and Testing) to the existing Issue type schemes, then you can make use of Bulk edit option. Users with Move ticket permission can move tickets bulk from one type to another

i.e.

* In Main menu --> Filters --> Advanced search, write the JQL to get only Tickets you want to change type to Development and click search
* Click on the action menu ( 3 dots) and select Bulk Change

* Select all issues in the next screen and click Next 
* Select Move issues --> Next
* Select the required project and Issue type in next screen , click Next 
* uncheck "Send mail for this update" and then confirm

Nic Brough -Adaptavist- · Accepted Answer

Welcome to the Atlassian Community!

You do not change workflows by editing issues.

To use your new workflows, look at the "workflow scheme" for the project.  This determines the workflow association for each issue type.   Note that you have to do this via global admin, the options for workflows within a project don't let you do this because the workflow scheme is a global object.

It will have at least one workflow associated with "all unassigned issue types", which is the workflow any issue type not named later in the scheme will use.

Click "add" and add your two new workflows to the scheme.

If Story and Test are not already in the list, you can assign the new workflows to them as you add the workflows.

If Story and/or Test are already in the list, once you've added their new workflows, you can use the "assign" button to change the assignment to the new workflow.

Now click "publish".  Jira might ask you to migrate some status (if an old workflow contains a status the new one does not, it needs you to tell it what to move the issues to), but it will do all of the work of migration for you.

It's not "edit" you need here, it's "migrate", and it's all done by the workflow change process.