Status repeated in Issue search filter

[Heather Dubin]

I'm showing the same status repeat over and over in the status filter when I do an issue search. We do have the same status types repeated across projects. Is this why? If so, is there a way to clean it up? You can't filter by status this way. 

[Mikael Sandberg · Accepted solution]

Hi @Heather Dubin,

Welcome to Atlassian Community!

Yes, it looks like you have duplicates of the same status, and to clean it up you would have to identify which projects are using these statuses. The easiest way of doing that is to go to Settings > Issues > Statuses, from here you can see which workflows are using which statuses. I would recommend renaming the status you are planing to replace and remove to make it easier to identify the new one, then go to each workflow and replace the status.

[Heather Dubin]

Hi @Mikael Sandberg 

Thank you, but I actually need each project to have the same status, as each project goes through the same workflow.

Are you saying I can't have multiple projects with a "To Do", "In Progress", etc? 

[Jack Brickey]

not at all. you can absolutely reuse statuses and should. What someone has done is to create duplicates which is not necessary and ultimately results in the issue your are now experiencing. What Mikael is saying is that you need to combine duplicates into one. to do this you rename one of them to say "awaiting staging old". in this way you can more readily move them to the "awaiting staging" that will remain.

[Mikael Sandberg]

You can reuse the same status on multiple projects.

Do you know if you are using both next-gen projects and classic projects? I just tested it in my test environment and the basic search will list the same status multiple times if you are using next-gen projects. If you switch over to JQL search you will not see the duplicates.

[Heather Dubin]

we are using Next Gen projects. I suspect the duplicated workflows came in as we were testing things and then discarded projects that didn't work for us.

I can't ask my team to only use JQL search, and I'm not sure I'm following about combining them and duplicating the old ones. Any chance you can give me some better step by step instructions? Maybe with screen shots? 

[Mikael Sandberg]

Okay, so unfortunately there is no way of hiding duplicate statuses when using the basic search, and since you are using next-gen projects you cannot combine the statuses. Each next-gen project is its own island so to speak, nothing can be shared between the projects. There is a request to get this fixed, JRACLOUD-74037, you would see the same thing happen if you searched on custom fields with the same name. Go to the issue and add your vote to it if you want to see if fixed too.

[Heather Dubin]

Well, thanks for the info, but that's extremely unfortunate and incredibly frustrating. I'll vote for the fix, I guess. 

[Jack Brickey]

@Mikael Sandberg, yep that makes unfortunate sense.  Can you imagine 10, 20, 50, 100 NG projects all w/ To Do, etc. YIKES! the trials and tribulations of NG. :-(

NOTE: in my opinion there should be a separate issue from the one you offered. I think having duplicate statuses is much worse as I believe that 90% of NG projects will share one or more statuses with other NG projects whereas custom fields stats will be much less typically.

[Heather Dubin]

@Jack Brickey you're right that these are two different issues and it would be great if JIRA could fix both. From a PM perspective, it's a little ridiculous that each project in NG is an island unto itself. If a team is using all NG projects, of course they're going to have commonalities and you'd want to be able to see things across them. 

In the short team, I wonder if maybe there could be an error message when you call a status a similar thing as you have before? It might at least warn people that this might become a problem. 

In the meantime, do either of you have any suggestions on a work-around? I can't have my team wondering which status to filter by, and if they have to guess each time, or go to a JQL search just to see a list of tasks by status because of this, they're going to get frustrated and not use the tool.

[Jack Brickey]

Well I don’t completely agre with you her TBH. Not that I need to of course. The underlying premise of NG is that they are islands. This supports the idea allowing anyone to create and admin a project. So as not to effect other project. I sure hope that NG doesn’t evolve into a near-classic model where anyone, regardless of experience and accountability can make changes in their project that ultimately impacts other projects. On that day I shut of NG for my site. ;-)

I don’t have any ideas on a work around unfortunately.