I have a couple of crucible projects. To each of these projects a specific group of users should be assigned that is able to access this project. Other users that are not member of these groups shouldn't be able to view or event create a review in this projects.
Right now I am handling this by creating a permission scheme for every project with the only difference in the group of users that is assignerd to the 'create' and the 'view' role.
I find that a little bit cubersome, since there is already a configuration in the project itself where you can define the group of eligible reviewers but this configuration seems to have no effect for the 'create' and 'view' role. Why is there not simply another configuration option in addition to the groups of reviewers where one can define the group of users that is allowed to create reviews, so one could use one single permission scheme for all these projects? Am I doing anything wrong here?
We use the 'groups' functionality in Crucible and name it after the project. Like for project "ABC", we set the "Default Reviewer Groups" for the group named "abc_group" and it works perfectly well for us. Are you saying otherwise?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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