-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
3
-
Hi everyone,
Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Data Center.
We spend a significant amount of time determining our product investments in Bitbucket Data Center. Unfortunately, we are not planning to address this suggestion in the next 12 months.
I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.
In the meantime, we suggest checking free bitbucket-project-lock-plugin in Atlassian Marketplace, which disables changing project keys. It should be a satisfactory solution for many of you.
Cheers,
Anton Genkin
Product Manager - Bitbucket Data Center & Server
Original suggestion
We want to allow an specified group of project-members to be able to create repositories by them self. But they should not be able to change the projectkey as the projectkey should be always equal in our toolchain on a project (jira, confl, bitbucket, bamboo... even more tools).
The current permissonmanagement doesn't allow this.
- duplicates
-
BSERV-3055 Add setting in Stash Administration to disable changing project keys and project names
- Future Consideration