For the repositories of my team, I would like to make it possible for my developers to see which projects their repositories are assigned to. However, it seems that the ability to see projects is coupled with the ability to create new repositories, which seems to a global right. I.e. if a developer has access to even one of my repositories and is allowed to create new repositories, he/she is able to see all of the company's projects.
Since we organize our resources on a need-to-know basis, this isn't ideal. So far, the only solution I have found, is to not give anyone the right to create new repositories. This, however, leads to a situation in which only our administrators can see any projects at all.
I would like to establish the following situation: Developers can not create new repositories, but they can see projects (i.e Project names), if they have access to repositories within these projects. Is this possible?
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
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