Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to enable merge checks to make JIRA ID mandatory in description for each Pull Requests

vaski nath
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 28, 2021

Hi All,

 I am trying to setup Merge Checks for my specific bit bucket project so that any pull request which is getting raised should have valid JIRA ID reference.

I found few documentation but its not very clear. 

hence, is there a way to require jira issue keys for pull requests only and not for every commit?

Regards

vaski 

2 answers

1 vote
Ulrich Kuhnhardt _IzymesCo_
Atlassian Partner
September 28, 2021

Hi Vaski,

obviously the built-in merge-checks can't do what you need. You can follow steps on the documentation page by adding a merge check by way of adding an app. Some of them are free like "Better Commit Policy for Bitbucket" and you can configure the merge check once it is installed. 

I personally haven't tried them out - so I don't know which one exactly fits your requirements.

Hope that helps,

Kind regards, Ulrich

www.izymes.com

0 votes
Levente Szabo _Midori_
Atlassian Partner
September 29, 2021

Hi @vaski nath 

As @Ulrich Kuhnhardt _IzymesCo_ mentioned, (thank you!), the Better Commit Policy apps are dedicated apps for commit verification. By keeping all commits to your custom standards, you can make sure that all commits that end up in your Bitbucket repository have a Jira issuekey reference - or comply to even more rules!

You can start learning about Better Commit Policy for Bitbucket in the documentation.

This app is basically a connector for the main app, Better Commit Policy for Jira, so you need both apps installed to implement your commit check policy and rules.

In case you have any questions, or run into any problems, reach out to us anytime!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events