Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
37
-
Description
Hi everyone,
Thank you for your feedback. We appreciate your input and understand the importance of addressing our users' suggestions. Unfortunately, we don't have plans to address this specific suggestion in the next 12 months.
However, I want to assure you that your feedback is valuable to us. Over the last 12 months we have successfully implemented many highly voted suggestions including code-owners, resolvable comments and auto-merge and our upcoming roadmap includes a number of other top voted suggestions including dark theme, draft pull requests and multi-line comments. For the most up-to-date information on what features are coming soon please visit our roadmap.
Once again, thank you for sharing your thoughts with us. Your feedback plays a crucial role in shaping the future of our product. We do continually review these priorities and will continue to do so over the coming year to determine when and how we might be able to address this idea. You can learn more about our prioritization process here.
Cheers,
Sarah Bolt
Product Manager - Bitbucket Data Center
Original request description
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
-
- Closed
-
- Closed
-
- Closed
