Crucible permission scheme per project.

Hi,

I have an issue with Crucible permission. If I configured to disable "All logged in user" to View project. I cannot access the project anymore.

Is it possible to configure permission scheme alone with Crucilbe project permission?

What is the different between View permission inside permission scheme and Allowed Review Participants inside Crucible permission.

Thanks,

-Hieu

2 answers

This widget could not be displayed.

For example if I disable "All logged in user" in View permission of permission scheme. I cannot access http://localhsot/fisheye/project/CR-Test

This widget could not be displayed.

Hi Hieu,

If you disable "All logged in users" in "View" permission, this means that only the review participants of that specific project (reviewers, creator, author, and moderator) are allowed to access it.

If you don't belong to any of these roles but still want to view the reviews (like, for example, if you're an Administrator), you can edit the "View" permission and explicitly add your user in the "Individuals" field. You can also add Groups of users.

What is the different between View permission inside permission scheme and Allowed Review Participants inside Crucible permission.

The "Allowed Review Participants" field is where you can adjust who will be allowed to have a role (i.e. be an author/creator/moderator/reviewer) in this project's reviews. Only the users / groups you add here will be able to view the reviews of that project if you disable "All logged in users" in "View" permission (explained above).

More information about Crucible permissions can be found here:

Please let us know if you have any further questions.

Cheers,
Felipe Kraemer

Felipe,

Although I was member of project CR-Test but I cannot access this link http://localhsot/fisheye/project/CR-Test

Is there anything wrong?

Thanks,

-Hieu

@Felipe Kraemer - sounds like to keep projects restrcited you need a dedicated scheme with each project's LDAP group assigned to the "view". Just unchgeckuing "allow all" and setting the group to "allowed participants" doesn't actually make them participants. Bit of a chicken and the egg problem no? (Only authorized users can add participants, but no one except ad,mins are authorized to view it initially)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

85 views 0 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you