Kanban Collumns Showing Statuses That No Longer Exist in the Project

[Christian]

Hello All

I recently took over a Jira Instance that had many different workflows that were being unused, as there was a very unorganized approach to managing the Jira instance. Because of this, I noticed that when I made a Kanban Board with any filter other than selecting from a single project, there would be close to a hundred possible statuses that could be mapped to columns. 

Because of this, I went through the effort of remapping countless issues to new workflows, being able to delete many old workflows and statuses affiliated with them. Now, when I go to the "Statuses" section in my Jira Admin settings, I only see roughly 20 statuses in our entire site. However, When I go back to my Kanban board, or create a new one, I still see many statuses that are not on the site anymore or available to be even added to a workflow. Furthermore, many statuses are duplicated, even ones that are unique to only one workflow. It seems like broken functionality to me, but if there something else I can do to fix this let me know.

Thanks!

Christian 

[Trudy Claspill]

Hello @Christian 

In your Jira instance do you allow use of Team Managed projects? If so, such projects don't reference the globally defined Status value and Workflows. The Status values within those projects are unique and independent of the global Statuses, even if they have the same name.

If you are creating board filters that encompass Team Managed projects then you are likely picking up the Status values defined in those projects also.

[Holly Meza]

Hey @trudy_p I'm having this issue as well and we don't have any Team Managed projects. It's showing statuses for workflows that have been deleted and there are no issues in the statuses showing on the board. Any ideas?

[Trudy Claspill]

@Holly Meza 

Please start a new Question using the Ask a question button at the top of the Community page. Describe your situation completely and provide screen images to help illustrate your experience.

Creating a new Question will get your question better visibility to the wider community.

Adding to an existing post notifies only the original author, people who responded, and people watching the pust. That is a pretty small audience.

Also review the Community Guidelines to learn more about avoiding necroposting.

[Nicolas Grossi]

@Christian Try reindexing first and second, as you have an Premium licensee you might contact support.atlassian.com

Nicolas

[Holly Meza]

Hey Nicolas, in Jira Cloud there is no Reindex feature as they indicate it's done automatically. Any other ideas?