Current situation

As of today, when Bitbucket Server and Bamboo are integrated, repositories can be created in Bamboo, and Bamboo users with correct permissions can access all repositories in Bamboo. This can present a security risk for companies that don't want this level of access.

To workaround this situation, Bamboo administrators need to add an extra step for creating repositories that consist in:

• A Bamboo admin creating linked repositories, and restricting access to that repository.
• A Plan admin that can use those linked repositories in the plan.

This not only creates a dependency between administrators, it also doesn't cover the possibility to create plan repositories.

Accepted solution 1

Have a new level of permissions at an Application Link level that restricts bamboo users/groups on which repositories (or repository projects) to access.

Accepted solution 2

Have the possibility to inherit Bitbucket repository (or repository project) permissions in Bamboo, and use those permissions to restrict visibility to Bamboo Plan admins.