Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Disabling the select list of issue type based on user role/group

We need to restrict the user for creating the new issue type that we are developing. The users of specific role/group should only be allowed to create the issue type, and the issue type is getting selected through the select list i.e drop down. How to disable the newly created issue type value of this drop down for all other users and enable only for specific role/group users without any third party services/plugins?

1 answer

3 votes
Darryl Lee
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 23, 2023 • edited Sep 25, 2023

So there's a workaround documented that don't involve third-party add-ons:

  • Create/clone the workflow just for the new issue type
  • Modify the Permission scheme for the Project to grant an unused permission to the group (like Set Issue Security)
  • Add a Validator on the Create transition that limits it to only users with the Set Issue Security permission

What this will do will produce a nasty error when users in the "wrong" groups try to create an issue with the new issue type. It's bad UX, as others have pointed out.

Even if you avoided the permissions hackery by using add-ons like Workflow Enhancer for Jira or Jira Workflow Toolbox the users would still get a nasty error after they went and entered all their bug information. Again, bad UX.

I'm afraid the best solution would require the Behaviours add-on which does exactly what you want, and hides the particular issue type as you want, except for certain users. (https://library.adaptavist.com/entity/restrict-issue-types).

@Darryl Lee Thank you for the response.

Which particular validator needs to be used, whether it has to be JQL validator or permission validator?

If it is JQL query, what is the query to be used for Group users validation?

Darryl Lee
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 25, 2023

Hi, I had the wrong answer linked above, but in this one:

https://community.atlassian.com/t5/Jira-questions/Restricting-issue-creation-of-certain-types-based-on-user/qaq-p/32785#M13890

Paul writes that he used the "User Permissions Validator".

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events