Merge workflow status's

We ended up with two workflow status that mean the same thing - Reopened and Reopen.

Is there a way to merge these two status's so I do not have to copy, edit, and republish every workflow we want to change?

1 answer

1 accepted

1 votes

No, they're independent status objects, you'll need to add one of them to the workflow, move all the transitions from the one you want rid of, then remove the old one.

Thanks Nic, I suspected that was the answer, but was hoping for something different :)

Hi everyone,

Nic's answer is correct, but having just been through this I wanted to add some detail and an alternative to hopefully save people some time.

In our case, we had "To Do" and "Backlog" statuses in use and wanted to merge them, replacing "Backlog" with "To Do". As Nic says, you can add the new status to the existing workflow and then transition all issues to the new status and switch all your transitions over to the new status. However, you can have a couple of problems:

  1. JIRA only supports bulk changing 1000 issues at a time (you may be able to change this limit, I'm not sure). Hence you can spend a lot of time bulk changing these issues in batches.
  2. You won't be able to delete the old status from the workflow as the workflow is active.

If you have fewer than 1000 issues and don't care about leaving an isolated, unused status in your workflow then what I'm about to say doesn't matter. However, an alternative to the above is to copy your existing workflow, delete the old status and replace it with the new one, and then swap the old workflow for the new one in each workflow scheme that it's used in. As part of this swap in the workflow scheme, you are asked to map old statuses to new ones, and JIRA takes care of this automatically. I think the only cost of this way of doing it is that you cannot rename workflows and hence you won't be able to keep your workflow name, I just added a "2.0" to the end of my workflow. If you really wanted to keep the name you could copy the workflow, reassign workflow schemes to it, delete the old workflow, then make a second copy and use the original name, make any changes, and then swap back over to this workflow, but I was too lazy to do this :).

Hope that helps! And please let me know if I've missed something in going for this approach.

Cheers,

Paul

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,801 views 11 18
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot