Hi Team,
Please share the steps to restrict all the users (except admins) to create Priority 1 - critical issues.
In other words, we need that most of the users should not have the ability to create a critical bug.
Thanks,
Chakshu
You can't.
Some people try it with javascript, but that's an ugly hack that people can easily bypass. The best you can do is remove "priority" from the edit screen, then find/write a validator which you can put on transitions - you can code it to see if the priority is changing to "critical" and then check if the current user has whatever it is that lets them set it (member of specific role?) and refuse the transition if they fail the check.
I said find/write - frankly, use the script runner plugin, it's really quite easy in that.
Thanks George and Nic for your quick response.
Please let me know the steps to restrict users to create the issue of a particular "Issue Type".
According to requirement, all the issue types would appear in the Issue type selection drop down. But, as soon as any jira user chooses some issue type, Jira should validate that whether this user is authorized to use that particular issue type or not. And accordingly give him the message.
So, can we restrict users to create some issue type, and restrict creating the other issue type, depending on the user role.
Thanks,
Chakshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a totally different question.
It's also one you can't do though. Issue types are limited by the PROJECT you are in. That's it.
The best you can do is block issues from being created, after the user tries to do it - put a validator (again, script runner is your friend!) on the create transition that can say "if user matches X, fail". It's clunky because the user has to go in and try to create the issue before being told it won't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, there are no simple steps for it - it should be made a development - custom validator, that wouldn't allow to create issue with such priority.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.