Details
-
Suggestion
-
Resolution: Fixed
-
107
-
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 Server.
We spend a significant amount of time on an ongoing basis to determine our product investments in Bitbucket Server. Unfortunately, we are not currently planning to address this suggestion in the next 12 months. In the last 12 months, we've resolved 10 of the top 30 feature requests, and our upcoming roadmap includes a number of other top voted suggestions, including in-browser editing, improvements to search functionality, better JIRA integration, and providing an even better code review experience.
I understand that this may be disappointing, but we believe it’s important for us to be open, honest and transparent with our customers. Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here.
Norman Ma
Product Manager - Bitbucket Server
Original request description
With stash 1.3, the description put into a pull requests only exists in the request. This description should be put into the commit message.
Attachments
Issue Links
- is duplicated by
-
BSERV-8827 Pull Request Title(not the default one but edited) to be in pull request commit message
- Closed
- is related to
-
BSERV-10184 Ability to set a default merge commit message
- Closed
- is resolved by
-
BSERV-10559 Allow configuring a pattern for pull request merge commit messages
- Closed
- relates to
-
BSERV-10559 Allow configuring a pattern for pull request merge commit messages
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...