Limit use of priority's

[Wayne Griswold]

Hello! I was wondering, is it possible to limit the uses of certain priority's? I have a Major priority, but I would like users to only be able to have 3 or less of those at one time, to not get overloaded with work. Is such a thing possible? Thanks!

[Nic Brough -Adaptavist-]

Not really.  There are some javascript hacks and add-ons which will limit the list, but it's getting easier and easier to get around those.

The other option is to use validators in the workflow to check and reject updates, but that won't stop edits.

[Wayne Griswold]

There are some javascript hacks and add-ons which will limit the list

What are those?

[Nic Brough -Adaptavist-]

They are snippets of javascript code which you add to the announcement banner. They execute in the browser after the page loads, and can be used to remove options from the priority list. I only mention them in my answers because if I don't, someone else will mention them and suggest that they're actually a good idea (they are not, and if anyone tells you they are, they're wrong) - The code is highly volatile, the slightest change can break them, including upgrades, addons and other snippets - They run in the browser, so a user can easily bypass or ignore them - They run in the browser, so REST ignores them - There is often more than one way to create or update an issue, and covering every possible route with javascript hacks is a nightmare, especially when you often need different code for each route. (See the first and last points for why I'm not giving you any code)

[GabrielleJ]

Try the Behaviours plugin https://marketplace.atlassian.com/plugins/com.onresolve.jira.plugin.Behaviours. I think it's not allowed out of the box.