Before you will merge or push your changes you need to check the corresponding Jira issue. Establish and protect your workflow
Before you will merge or push your changes you need to check the corresponding Jira issue. Establish and protect your workflow
Before you will merge or push your changes you need to check the corresponding Jira issue. Establish and protect your workflow
Merge and Push configuration
Merge Protection
Push Protection
The merge and push hook settings enables you to configure the following checks:
Issue key, Issue status, Branch naming convention, Squash commits, Merge commits, Jira JQL, Rebase branch, Commit message syntax
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.
Merge and Push configuration
Merge Protection
Push Protection
The merge and push hook settings enables you to configure the following checks:
Issue key, Issue status, Branch naming convention, Squash commits, Merge commits, Jira JQL, Rebase branch, Commit message syntax
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.
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 cloud
(10)Sign in to write a review
Hi Eric,
thanks for your feedback. This requirement has been implemented in the version 4.2.0.
Please evaluate it and let me know if it fits to your needs.
Benjamin
Reviews for server
(10)Sign in to write a review
Reviews for Data Center
(10)Sign in to write a reviewHi Eric,
thanks for your feedback. This requirement has been implemented in the version 4.2.0.
Please evaluate it and let me know if it fits to your needs.
Benjamin
Pricing
| 10 users$10 | 25 users$85 | 50 users$170 | 100 users$340 | 250 users$680 | 500 & upAdditional pricing details |
| 10 users$10/year | 25 users$85/year | 50 users$170/year | 100 users$340/year | 250 users$680/year | 500 & upAdditional pricing details |
Paid-via-Atlassian 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 more details about qualifying for special licenses, see here.
- Can I extend my free trial?
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.
Paid-via-Atlassian pricing FAQ
- How does Data Center app pricing work?
Data Center pricing FAQ
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 Data Center pricing?
Data Center pricing FAQ
- Do you offer academic, community, or open-source licenses?
Data Center pricing FAQ
- Can I extend my free trial?
Data Center pricing FAQ
DevOpsSystems Mueller provides support for this app.
DevOpsSystems Mueller provides support for this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Versions
Version 4.2.6 • Bitbucket Server 5.2.0 - 5.12.0 • Released 2018-07-02
Summary
Maintenance Release
Details
Bugfix- JHFB-66 - Migration of 3.x settings not always successful
Attention:
If the merge hook has valid settings, the merge hook will be enabled automatically after the migration. If there are valid settings but you do not plan to use the merge hook, you need to disable the merge hook after the update.
Versions
Version 4.2.6 • Bitbucket Data Center 5.2.0 - 5.12.0 • Released 2018-07-02
Summary
Maintenance Release
Details
Bugfix- JHFB-66 - Migration of 3.x settings not always successful
Attention:
If the merge hook has valid settings, the merge hook will be enabled automatically after the migration. If there are valid settings but you do not plan to use the merge hook, you need to disable the merge hook after the update.
Installation
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Jira Hooks for Bitbucket via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Jira Hooks for Bitbucket. You're prompted to log into MyAtlassian. Jira Hooks for Bitbucket begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Jira Hooks for Bitbucket versions compatible with your instance, you can look through our version history page.
- Log into your Bitbucket instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Jira Hooks for Bitbucket via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Jira Hooks for Bitbucket. You're prompted to log into MyAtlassian. Jira Hooks for Bitbucket begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.
To find older Jira Hooks for Bitbucket versions compatible with your instance, you can look through our version history page.
Similar apps
