nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to delete unused statuses from portal filter

Clément GENTIL

Hello everyone

I wonder how to delete these unsued status from the client portal.

When a user tries to filter, he is seeing unused status in the project workflow.

As you can see in the second screenshot, i already deleted these status. But they are still listed in the available filter statuses.

Of course, the user is only member of a project with the status above. However, he was previously a member of another project for some tests.

Thank to anyone who could help me !

Accepted answers

Clément GENTIL

Ok i found out.

Duplicate statuses were linked to the name showed to customer in

Request type → (Any request type) → Workflow Statuses

Having different names accross all existing request types (or none) was the issue.

Each different name is shown to customer as different statuses, even if it's the same main one

(which is actually legitimate)

All comments

Chris C__0601um

huh on ours I can only "Edit".. I am an admin of all the things.

I do wonder though, if you have a status that is NOT associated with any workflow, would you get a new option to Delete? I would think if you deleted a status that was used in a workflow, it could have a detrimental effect on that workflow. So if you edited the workflow to not use that status anymore, and thus the Status was no associated with anything, could Jira then allow you to delete it?

If your's is already like this with no associations, and still doesn't let you delete it, please let us know. I don't want to make a test one now, just to be stuck with it forever

Clément GENTIL

I am actually able to delete statuses that are not associated to any workflows:

I can't see the "empty" status on the filter list created for the test.

I got no results when searching for a request type listed

Maybe this status was previously used in the workflow imported from a template by a service provider when he set up our JSM.

It makes sense that JSM keep it somewhere store it if it was previously used but none tickets have this exemple status.

Our customers see unused status and are confused when trying to filter their requests.

Chris C__0601um

Awesome! I was hoping that would be the case.

I don't know why your customers would be seeing ALL the statuses. That isn't helpful, as you've noticed. Could it be because those other statuses are available on other projects that customer might have access to?

Clément GENTIL

Tried with an other project in our instance → adding other statuses to the filters.

I don't think this customer was added to other instances since it is a portal only custommer ?

Clément GENTIL

Our project is already restricted because only pre-provisioned users needs to access the portal.

The thing is, there is absolutely no way customers can have tickets with these statuses.

They are not in any workflow of any projects anymore.

They were in the workflow but i deleted them few days ago.

post error

Clément GENTIL

Ok i found out.

Duplicate statuses were linked to the name showed to customer in

Request type → (Any request type) → Workflow Statuses

Having different names accross all existing request types (or none) was the issue.

Each different name is shown to customer as different statuses, even if it's the same main one

(which is actually legitimate)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management