We're trying to set up a new environment using Crowd as master user repo (with delegated auth to AD), and connecting amongst others Jira to this.
Under Application Permissions, Jira is set up to allow all modifications to the delegated directory server. What we would like, is for some project administrators to be able to modifiy a group which decides who has access to the source code repo (Stash and subversion).
We can't seem to find out how to set this up, if it is possible at all. It would be quite tedious to rely on the crowd administrator to assign new jira project participants to particular source code repos. It would be better if this responsibility was delegated to the project owner in jira.
How can we do this?
I don't believe there's a great way to do this currently without some heavy customisation. There's an open feature request in Crowd (CWD-2897) to allow specific users to change memberships for a group without giving them full administration rights; please comment and vote if this would cover your case.
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