How to remove statuses marked as 'Workflows applied (not editable)'?

[Nick]

In Jira settings / Issue attributes / statuses we see a large number of statuses with 'Workflows applied (not editable)' under the 'workflow' column as they do not give us the option to delete them.

This would appear to indicate that they are being used in some workflow however we have reviewed all workflows as well as all statuses defined in 'next-gen' projects and they do not exist. We recognise the status names as ones we created before so they are not system statuses.

My guess is these are orphans from previous next-gen projects that were deleted. Is it possible to remove these statuses?

[Earl McCutcheon]

Hi Nick,

This happens when a workflow has a status without outgoing or incoming transitions, and then cannot be edited while active.  Some more details can be seen in the following KB article:

• "Cannot Add Transitions or Delete Steps in Draft Workflows"

But the best way to make the edits is to copy the existing workflow so you have an inactive workflow copy to make the edits on then swap out the inactive workflow for the modified version in the workflow scheme.

Regards,
Earl

[Nick]

Hi Earl,

Thanks. However my point was that these 'statuses' do not exist in any workflow. I've been through every active and inactive workflow and they are not there.

[Earl McCutcheon]

Hi Nate, 

Thanks for the clarification and I misread that the first time, and this is odd behavior.

We did a bit of testing and digging on this one, but neither I nor my associates have seen this particular behavior before and we want to take a closer look at the data on your site to see what is going on as looks like a new Bug on the surface.

I created the following Support request on your behalf, can you upload a screenshot of the statuses page on the request and one of our support engineers will reach out to you shortly to go over the findings:

• https://getsupport.atlassian.com/projects/PSCLOUD/queues/issue/PSCLOUD-34315

Let me know if you have any issues accessing the request.

Regards,
Earl