Improve prefilled title from branch name when creating multi-commit pull request

Issue #14357 closed
Thomas Sondergaard
created an issue

If the PR contains multiple commits, bitbucket currently uses the branch name to pre-fill the Title field. This leads to poor titles in many PRs for us, because branches may have names such as feature/<jira-issue-key>-<very-short-desc>. It is very easy for developers to forget to give their PRs good titles this way.

Comments (4)

  1. Alastair Wilkes staff
    • changed status to open

    Hi Thomas,

    Generally take the view that any prefilled information is a helper - it's not permanent, you can change it (even after the PR is removed).

    Right now we think there is more value in keeping it (since it includes the JIRA key, which people forget to include a lot), so we're not going to remove it. That said, we could make the prefilled value more useful.


  2. Thomas Sondergaard reporter

    The problem is that developers tend to overlook that the prefilled title is not very descriptive. If the prefilled title can be made better, that would be great. If all or maybe just most of the commits reference the same jira issue that issue could be used to prefix the title and perhaps the summary of the jira issue could be used for the PR.

  3. Alastair Wilkes staff

    For now, I'm going to go ahead and close this as there hasn't been much activity, there isn't a clear path to improving this, and we are focused on other items at the moment.

  4. Log in to comment