Custom Pull Request Description Template (BB-14637)

Issue #11571 open
Ben Tatham
created an issue

Lately, a bullet list of the commit messages has been added to the default description of a Pull Request.

This is great, but we'd love to have our own template, that might include some of this dynamic data, using some parameters like ${commits} or something.

We typically include multiple headings in all PRs for our team, and it would be nice to have that auto-populated.

Comments (63)

  1. Zachary Davis

    This is not currently on the roadmap, and as far as I know there isn't any current plan to add this functionality. This doesn't mean we never plan on doing it, or that we don't think it's a useful idea. It's just not at the top of our priorities right now.

  2. Marie Fetiveau

    Also interested by this feature. Our PR template is static, right now we are copying / pasting it from Confluence, but could be really helpful if it is already here in the description when we create the PR.

  3. WeiningMa

    We'd love to have this feature also. We are using a static PR template right now and every time people need to copy/paste.

    BTW: @Peter Ramsing, we have also tried the Chrome extension but it doesn't work though. Creating commit first then do PR but there is no template added into the PR... Any idea?

  4. Sravan Manne

    +1 We are looking forward for this feature as well. -To be able to define sort of a "Description Template" for the developers to provide some mandatory details while raising a PR.

  5. bartread

    +1 for this feature. -1 for the yak-shaving I had to go through to add a comment to it.

    Seriously, it's been incredibly useful with GitHub. I have, however, a client who uses on premise BitBucket and for whom GitHub isn't really an option (in theory they could migrate to on premise GitHub Enterprise, but it's kind of a pain in the neck). This feature would be incredibly useful for them as well.

    I've previously worked on teams where you can use it to include, for example, a checklist of actions to be completed/considered before submitting a PR, which can help make the code review and approval process run smoother.

  6. Manuel GΓ³mez

    Ok, unsusbscribing after months of daily "+1"s and no f's given by BitBucket team.

    For this and other issues, my organization is moving to git and will use a more mature and user aware solution, as GitHub, Gitlab or whatever, anything will be better than this.

    Good luck!

  7. Chris Werding

    What I am wondering is why nobody (no staff) is managing this proactively? And it's not like we would be talking about some super scary special feature? This, along with BB-14755 is just so obviously useful that I am really wondering what's the issue here? Feature parity with Github would be SO important, dear Atlassian!

    Reminds me of Hipchat, a couple of years ago. Hipchat was ok, the integration with Jira was good, the client really bad (in it's early days). And instead of any progress, it just sat there and nothing happened. And then came Slack. And that was it, basically, for Hipchat.

    So dear Atlassian, how can we help? We would love to, really. Otherwise, we wouldn't be posting on your support forums all day long, right? :-)

    Best, .chris

  8. Log in to comment