-
Suggestion
-
Resolution: Unresolved
-
None
-
12
-
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.
In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request description templates, capability to enable/disable source branch deletion on merging pull requests and our upcoming roadmap includes a number of other top voted suggestions, including repository archiving. Please check out our public roadmap for more details on the coming soon and future items.
In the meantime, we suggest you checking Submodule Changes for Bitbucket in Atlassian Marketplace.
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.
Cheers,
Anton Genkin
Product Manager - Bitbucket Data Center & Server
Original suggestion
I create a pull request in a repo that has submodules located in another project in Stash. I click on diff and it shows the diff of the submodule but it only shows the commit hash diff. It doens't actually show what changes were made to the submodule.
- is duplicated by
-
BSERV-8720 Bitbucket submodule pull enhancement
- Closed
- relates to
-
BSERV-9660 Submodule feature branches and pull requests.
- Gathering Interest