You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi all,
I want to restrict creation of specific issue type only for users having administrator study role. Can someone help me with the same?
I tried the following steps :
Tried giving permission for study but that's affecting all the issue types.
Tried adding workflow property for create used the following property : jira.permission.create.projectrole=10303.
But even that doesn't seem to be working as that property was getting overridden by project role permission I guess.
basically, on creation if project role is administration then specific value shouldn't be shown in the drop-down of Issue type dropdown in create screen.
.
Is there any other approach which can be only applied to particular issue type but not other issues.
Note - client doesn't want to have it implemented using any add-on plugin.
Hello @Reeta Kumari
Jira does not have a native solution for restricting the issue types that are available in the drop down list in the Create Issue dialog. If the issue type is not a sub-task type of issue, and is one of the issue types available in the project, then it will show up in that list.
The only related option without using a third party app is to put a Validator into the workflow (for a Company Managed project) that will block saving the issue based on its type and the user's project role. However that will not be engaged until after they click the save button within the Create Issue dialog, after they have entered the data they want to put in the issue.
There is no clean way to do it without an add-on. I remember seeing a post using issue security scheme that will disallow the creation AFTER it is selected. The only really good way is to put that issue type in a separate project
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.