Save time with default pull request descriptions

[Alastair Wilkes]

Hello community!

I'm excited to share that one of our mostly highly voted feature requests for pull requests in Bitbucket Cloud recently shipped: default pull request description templates.

This feature saves times for both authors and reviewers. By providing a template of information to fill out, authors can open pull requests faster with less guesswork. And more information in the description helps reviewers understand changes faster.

You can set a default description in your repository settings. Happy coding!

Alastair
Bitbucket PM

[Gonchik Tsymzhitov]

Hi @Alastair Wilkes, 

Thank for the present :) 

Cheers,

Gonchik 

[Tyler]

Awesome!

Are there any variables available? I would like to be able to list commits as before but with extra options.

Best,

Tyler

[Antoine Letouzey]

same question. can we access source/target branch names, list of commits, ect ?

[Sebastian Penhouet]

As this was left unanswered by @Alastair Wilkes, here a new discussion thread: Variables in default pull request descriptions? (atlassian.com)

[Alexei Ferreira]

Great!

   Will this feature be added on bitbucket server too? If so do you have a date already?

Thanks!

[Alastair Wilkes]

Apologies for the very late reply, but you can watch this public issue tracking this request for Bitbucket Server: https://jira.atlassian.com/projects/BSERV/issues/BSERV-8663

Thanks!

[Jonas De Kegel]

"gathering interest"... 

[Juergen Lanner]

... watching a dead horse which starved only 5 year ago ...

[alrocha]

Hello @Alastair Wilkes,
in that link that you have shared (a year old and 352 votes, ain't is enough to develop that feature? asking without any idea of how you measure acceptance of requests) would that include Bitbucket Data Center Instance?  

[Deleted user]

Doesn't seem like questions are being answered here, but I'll throw mine in, too: is this feature only available on a repo-by-repo basis? I'd love to not enter the same default description a dozen times.

[Alastair Wilkes]

Hi Ross,

For some reason, I have not been receiving email updates for this post. My apologies. At this time, it's just a repository level setting.

Thanks,

Alastair

[Rupert Broad]

Would be even better if you could have a markdown file in the root of the repo that populated this Description automatically. Just like Github does.

[Des]

@Alastair Wilkes How do I enable this for BitBucket Server? Thanks.

[Alastair Wilkes]

Hi Des,

Thanks for your question. This feature is not available for Bitbucket Server, but you can watch this public issue to learn more about its status: https://jira.atlassian.com/projects/BSERV/issues/BSERV-8663

Thanks,

Alastair

[duy9403]

Hello @Alastair Wilkes ,

When using this feature, the list of commits is replaced by the default description. Is there possibility to add option to append the list of commits after default description, or I should create a suggest ?

[Alastair Wilkes]

Hi,

There is an open feature request for this here: https://jira.atlassian.com/browse/BCLOUD-17743

Thanks,

Alastair

[Jody Tate]

Our team would like to see the ability to set a default PR template for multiple repos at once, e.g., the ability to set a default PR at a workspace level. 

[Amit Alon]

Hello @Alastair Wilkes,

in the Bitbucket repo setting page, under Pull request description template there are 2 options on the template behavior to choose from:

Use the commit history as the default description
or
Create a custom description template

As others asked before I am asking as well: Is there a way to combine both options, i.e. allow adding custom description template on top of (above) the commit history, as the default description provided for each PR?

I am sure that doing this change will greatly help many developers around the world, and since both options are already implemented by Atlassian, adding the ability to combine them can be done easily by Bitbucket developers.

...And if this ability is already available, please explain how to use it.

Adding also @Christian Glockner and @Graham Gatus as ATLASSIAN TEAM reps, since I am not sure if @Alastair Wilkes, is still working at Atlassian - his replies are very old.