Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
Description
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
This is critical issue for our organization.
We have about 271 projects in Jira.
Each project in Stash has exactly the same key like in Jira.
To prevent incoherence I would like to disable changing poroject keys and project name (optional).
I see this as two checkboxes in Stash system administrator panel:
[ ] Allow Project Administrators to change Project Keys [v] Allow Project Administrators to change Project Names
Attachments
Issue Links
- has a derivative of
-
- Gathering Interest
- is duplicated by
-
- Closed
-
- Future Consideration
- was cloned as
-
- Closed
