How can I clean up duplicate Status values

[Corey Hill]

When updating the Status of an issue, some of the statuses have what appear to be duplicates. For example we see "QA in Progress" and "QA in Progress (2)" and I can't figure out where to go or what to do to get those duplicates removed.

[Clark Everson · Accepted solution]

Hi @Corey Hill 

Welcome to community!

Unfortunately this is one of the many hardships of being a Jira Admin. This is a pretty manual task. What you would need to do is go and add "QA in Progress" to all workflows where "QA in Progress (2)" is used with a transition from "QA in Progress (2)" to "QA in Progress" and moving all transitions from "QA in Progress (2)" to "QA in Progress", basically disabling the status.

Then you would bulk change all these issues. Then you delete all the "QA in Progress (2)"  from the workflows.

Best,

Clark

[Corey Hill]

Hi @Clark Everson 

Thank you! After some more poking around, I think the duplicate values were showing up because each status had multiple transitions or an "All to status" transition. So when you go to change the status on a ticket you'll see multiple transition options for the same status.

[Clark Everson]

Hi Corey,

so yes and no. Only if transitions or statuses have the exact same name do they get the (1)

having multiple incoming transitions including all transition will not be the cause of this. The all transition will not have that name or cause this issue. There can actually be very valid reasons for there to be an all transition then a singular transition, though it’s not often used.

if you don’t reuse statuses though or have the same transition multiple times it can

i would suggest looking at all the statuses in your instance and every workflow as well

if you work in sprints I’d probably recommend giving yourself some spikes to research your instance. You probably only scratched the surface of what you need to cleanup to be honest.

I wish you the best of luck and if you hit questions always feel free to come to community.

but to put it bluntly this is an average, if not minor Jira admin day in the life task.

best,

clark