Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
93
-
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. In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request 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. Check out our public roadmap for more details on the coming soon and future items.
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,
Imran Khan
Product Manager - Bitbucket Data Center & Server
Some complicated projects are setup across many repositories and it can be both cumbersome and error-inducing to manually submit and merge Pull Requests(PR). Somehow allowing for a single entry point for PRs at a project level would be a huge boon for larger projects.
-When a PR is created, check to see if PR should also be created in other repositories of project.
-When merging, merge related PRs in project.
Other systems enforce same branch name for linking PRs together. Obviously only checking for open PRs, not closed, nor merged.
Attachments
Issue Links
- is duplicated by
-
BSERV-5388 Link PR between projects so that changes in dependant repos can be represented
- Closed
-
BSERV-7773 Add relationships to pull requests
- Closed
-
BSERV-9523 Group a set of PRs together as a logical unit
- Closed