Is any issue or commit message not as expected, the merge will be blocked. In the screenshot the warning message shows, that the related issue "TEST-1" is in the state "In Review" and the expected status is "Reviewed".

The hook will check, if a commit (or all commits) and the related issues are as expected. Is the commit or the issue not as expected (e.g. the issue is not in the correct status) the push will be rejected.

More details

What is the "Jira Hooks for Bitbucket" Plugin?

Jira Hooks for Bitbucketintegrates constraints into the Bitbucket workflow. The defined conditions ensure the integrity of a code change with the associated Jira issue. If a condition is violated (e.g. the issue is not in the correct state), a merge or a push is not allowed. Jira Hooks for Bitbucket thus enables you to support the development process defined in your company with defined rules.

Merge and Push Protection

You can configure the following checks in the merge and push hook settings: Issue Key, Issue Status, Branch Naming Convention, Squash Commits, Merge Commits, JIRA JQL, Rebase, and the Commit message syntax. The hook checks to see if the issue mentioned in a commit, in all commits, or in a branch is as expected. If the issue is not as expected (e.g. if the issue is not in the correct state), the merge or push is rejected.

Reviews for server

We ran into a unique issue related to application tokens. It took a few days to work through, and figure out what was wrong. Support stuck with the issue, was quick to respond, and provided a test fix that resolved the issue. Thank you!

Cloud Pricing

Server Pricing

Data Center Pricing

Pricing FAQ

How does server app pricing work?

Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

How do I determine my server pricing?

Apps are billed based on the number of users in your host product. The app tier should match the licensed user tier of the Atlassian host product. For example, if you have a Confluence Server license for 25 users, you should purchase the 25-user tier for apps. Even if fewer users want to use the app than your host product license, the two licenses should match exactly.

Do you offer academic, community, or open-source licenses?

For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

How can I buy apps for my legacy Jira Server or Confluence Server license?

If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

Purchase the app at the non-legacy Unlimited (10000+ users) tier.

Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

Vendor support resources

Contact

Versions

Version 4.2.7•Bitbucket Server 5.2.0 - 5.13.0• Released 2018-08-08

Summary

Maintenance Release

Details

Due to a refactoring from the major release 3.x to the major release 4.x, the merge hook got a new hook key. This is the reason, why Bitbucket can not find the already configured 3.x settings in the 4.x merge hook. But the hook settings are still available.The automated migration of the merge settings has been disabled. Alternatively we offer a migration guide wich enables you to migrate the settings from 3.x to 4.x