The requirement is to add a merge restriction to match the fix version of JIRA to avoid any merges that are not part of a specific release.
@PramadaK We have just released a new merge check which runs a custom JQL query and allows merging only if the work items are matching the JQL search results. It is part of the Better Commit Policy Connector app and it relies on the Forge custom merge check mechanism mentioned by @Ulrich Kuhnhardt _IzymesCo_.
For your use case, just use a JQL with the fixVersion field like this:
project = FOO and fixVersion = "1.2.3-beta"
It means that a PR can be merged only if the work item is in the FOO project and it has the fix version "1.2.3-beta". For example, merging is not allow here because the PR violates the policy:
You can configure it to check the PR title, PR description, commit messages, the source branch name or all of it!
(Discl. this app is developed by our team.)
Hi Pramada
I don't believe there is such a merge check that comes with Bitbucket cloud natively.
The good news is that Bitbucket cloud supports custom merge-checks based on the Atlassian Forge platform. You can write the merge-check exactly to your specifications and use it in your workspace. Since you're on a premium plan you can actually block merges that don't pass this merge-check.
Hope that helps.
Best, Ulrich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.