Avoid users creating new statuses

[PaulaA]

Hi, 

We have a lot of simplified workflows and because of that, we have too many statuses that are the same but written in different ways.
We want to prevent users (everyone) from being able to create new statuses. It should not be possible in any case.
I have tried to recreate the workflow and the schema but from the boards, the board administrators can still modify and select simplify workflow, and then add new states.
At the moment, the only way I have found is to add a state with a transition to itself that only jira administrators can execute (this way the users won't see it and it won't be confusing for them). It's not a very fancy solution but I can't think of any other way.
Has anyone managed to solve this in a more elegant way?
Atlassian doesn't seem to have this in mind for the next few months and there's no point in us admins trying to keep things clean if users can trash it over and over again.
Thanks

[Florian Bonniec · Accepted solution]

HI @PaulaA 

Disabling the Extended Administer permission should prevent user to add new Status in simplified workflow.

Also having the workflow shared with multiple project will prevent that.

Note that user will also lose the permission to add existing field to screen if they are not admin.

JIRA Admin will be able to create status but not Project admins.

Managing project permissions | Administering Jira applications Data Center and Server 9.11 | Atlassian Documentation

Regards

[PaulaA]

Hi Florian, 

Thank you but I have disable the extended admin rights and still on the boards they can select to simplify the workflow and there we go again.. they can still create new statuses. 

Ideally we would share more the workflows, but that's also part of the clean up but at the moment is not possible. 

From Atlassian support:

You will only be able to switch to Simplified Workflow if:

• There is only one project being viewed by your board (to check this, look at the board's filter)
• That project uses a JIRA workflow scheme which only has one workflow for all issue types;
• Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian (not any which are provided by add-ons)
• The existing workflow has at least one outgoing transition for each status

Usually this conditions are given, any idea on any trick nicer than the one I have proposed? It's not so nice as the users can still see the "hidden" status in the boards.. 

Thank you

[Florian Bonniec]

Based on this criteria, I would say that one way to do it will be to add 1 workflow in the Workflow Scheme even if it's a copy of the current one...

So if you have WF_Default for Epic and Story, make a copy of this WF and assign the copy to Story.

You could also add a dummy status in the WF with no transition to or out of it and it will prevent user to switch to simplified workflow.

If you have some apps such as scriptrunner or JSU, you could add a condition validator or postfunction that do nothing but will prevent the user to switch to simplified WF.

I do not have much idea, 

Regards