Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Allow domain users to be users in crucible

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?

2 answers

1 accepted

1 vote
Answer accepted

Please see my reply to Paulo above

Hi Aelliott

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

Cheers,

Paulo Renato

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

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....

5 views 0 0
Read article

Community Events

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

Events near you