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

How do you prevent project administrators from assigning (specific) user groups to project roles in

I want to restrict groups like "jira-users" used in the project roles. Is there any possibility with the scriptrunner. If yes then can you please help with the script.

1 answer

1 accepted

0 votes
Answer accepted
Clark Everson
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 14, 2022

Hi Ankush,

To my knowledge is no you can't restrict them adding groups to project roles. However the way we handle this in our company is from the permission scheme themselves. We have a public Jira instance and for our public projects the browse project permissions are visible to the jira-users group.

For the private ones the browse projects are only visible to the employees group. That way, if the jira-users group is added to a project role, the permissions for browse project trump the project level roles.

Hope this helps!

Best,

Clark

Hello @Clark Everson 

Is there any possibility with script runner.

To my knowledge no and we have scriptrunner. However even if you could that would be very bad practice. Using LDAP groups and built in functions you can accomplish this very easily. Whenever you use scriptunner you add overhead to your system that if done wrong can impact the system. 
I explained how to do it above but if you aren’t comfortable with that I’d recommend working with an atlassian partner to make your instance scalable.

scriptunner and other third party tools should really only be used on an as needed basis to maintain instance health. Not for things that are very easy to do with built in schemes.

Hope this helps! Sorry I’m posting from my personal account unintentionally 

Suggest an answer

Log in or Sign up to answer