We have been using fisheye/crucible for a couple years and are gettting back into JIRA, plus Confluence and want to utilize with Crowd with them for SSO via our Active Directory. Last week we edited the permission scheme (agile) so all users can view reviews. We are having issues creating reviews in crucible - we have a web-hook setup that executes a script in our code to create reviews automatically and it has worked fine with built-in accounts. Now after we have login with our Active Directory accounts and setup our tokens we cannot get reviewers for a given project. Any ideas on which permissions we need to setup?
If this process is properly running with a built-in (Crucible) account, you should be able to keep using it. However, just be sure that you don't have this same user account in AD side.
The application will try to find this user in AD. If not found, the server will look for the account in the internal directory, so bult-in account.
For further details, I would suggest to raise a ticket at support.atlassian.com
Thanks for your response.
We believe we have a solution for this - we ditched the Agile Permission Scheme and used the default after updating the roles so that most roles allow all user types (Reviewer, Creator, Author, Moderator (though we aren't using a Moderator)) to handle most permissions except the ones it wouldn't really apply (e.g. Create [review]). Then we had to update the script run by the web-hook to use our accounts from AD.
Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events