We are looking forward to simplify the way we manage our autorisation settings.
In that matter, we would like to know if there is any preferred autorisation settings from a performance point of view (we have a 500 users licence).
Our current use is : put our users into differents groups. Assign those groups to Project Roles. Then, attribute those Project Roles to Project Persmission into an Autorisation Scheme.
In terms of performance, the second solution is fine; at a large retail client I had 200+ projects and inherited that structure, which worked fine. Every instance is different, but what is useful to look at is how people are working in JIRA and the groups they are working with. Are they always working with the same people in the same groups, or is each man on his own, working in 5-10 projects, all different from the person beside him? If that's the case, the second setup could be better. From an admin perspective though, I'd have the first solution as the default.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs