Where are the Priority Schemes in JWM?

[Jonathan Smith]

My question is pretty straight forward :) Please tell me this functionality to limit the list of priorities per project was not removed.. 

Note: I am coming from Jira Core Server.

If  priority schemes were removed, please direct me to a best practices article as Google failed me. 

Cheers.

[Nic Brough -Adaptavist- · Accepted solution]

I've done both types of option in the past. 

For point 1 - yes, sort of.  You can have two different issue types and associate a different workflow with each (then one of them goes to ungroomed and the other to groomed on create).  The weakness here is that you can't stop your "unwashed masses" from using the groomed issue type.  The best you can do there is to have a validator that blocks the actual creation on some criteria (probably like "user is in power user groups/role") but they'll still be able to start creating the issue

For point 2 - not natively, but you can create a transition from ungroomed to groomed, protect it with a "only power users" condition and then ask them to use it when they finish creation.  You can build on that though, if you have the Script Runner, you can put on a "fast track" transition that can catch the create and automatically do the groomed transition.

[Jeremy Gaudet]

1) Not really.  There are ways, but all I can think of are fairly hack-ish.

2) In the "create issue" transition, you can use the 'fast track transition' script runner operation to move to Groomed, based on whatever criteria you want to include.  This could be based on role, group, field values, etc.