Details
-
Suggestion
-
Resolution: Unresolved
Description
Atlassian's model for Cloud products has two separate types of collections for users: Groups and Teams.
Groups are tied to IT structures for administration purposes and especially for integration with Identity management platforms (Azure AD, Okta, etc). Groups and group membership are managed by the administrators of the system.
Teams, on the other hand, are created and managed by users. Teams are smaller collections of users to define scrum teams, etc. Team membership can be managed by the owner of that team.
Groups in Bitbucket align more closely with groups in Atlassian Orgs and we are working to make groups shared across all products: Bitbucket, Jira, and Confluence.
We definitely want to implement Atlassian Teams into Bitbucket but this has not been prioritized yet.
I'd like to allow lead developers to be able to give other users access to the repos of the projects they lead.
E.g. we have "Good Lead Developer" who is not a company (i.e. Bitbucket team)-wide admin, but leads "Big Project". Now we have a "Big Project developers" user group with write access to all the Big Project repos. I'd like to allow Good Lead Developer to be able to add new users (from the team) to the Big Project developers user group. I don't want Good Lead Developer to be able to similarly administer any other user group and I don't want project team members to be added directly to repos (instead of user groups).
This doesn't seem to be possible now: you can either give a user group full admin access to all repos of a team, or the group can have admin access to certain repositories. The latter one however is not sufficient: this way they could only add people to the repos directly, not via user groups (which is generally a bad practice).
Maybe BCLOUD-2323 will also solve this?