Customers have installed this add-on in at least 1,055 active instances.
    by Benjamin Müllerfor Bitbucket Server 4.0.0 - 5.2.2 and more versions
    Versions available for Bitbucket Server 2.8.2 - 2.12.6
    Bitbucket Server 3.0.0 - 3.11.6
    Benjamin Müller supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    Get it nowFree add-on

    Check the corresponding Jira issue, before a action can be performed

    Check the corresponding Jira issue, before a action can be performed

    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

    The "Jira Hooks for Stash" plugin is a project, which aims the integration of Jira-Hooks in Stash. Especially checks regarding the integrity of a branch against the related Jira issue is the target. In several cases we have to check a lot of things regarding the related Jira issue, before we can push into a branch or perform a integration merge. Therefore this project has the target to provide a set of hooks, which checks the consistence of the issue before the action will be performed.

    To ensure the integrity between branch and the related issue, this hooks checks the status of the related issue. If this issue is in the correct status, then the merge/push is allowed. If the status is not in the correct status, the merge/push is not allowed.

    In the future there are a lot of further hooks planned, which will be implemented step by step.

    User reviews

    Sign in to write a review
    by Piers Hearn on 2017-05-24
    Unfortunately these hooks don't stop JIRA from creating branches that don't meeting our naming standards, only stops users from creating their own. Seems like a decent plugin otherwise.
    Was this review helpful?YesNo
    by Brian DeBlis on 2016-12-15
    It is great with making sure the Jira ticket is in the right state, but completely disables the auto merge feature
    Was this review helpful?YesNo
    by Eric Higginson on 2015-10-12
    Integral for the development process we're implementing. Would prefer if issues were tied through Stash or a branch name rather than the commit messages.
    Was this review helpful?YesNo
    by Tom Brandish on 2014-07-29
    Exactly what our project needs. Simple and effective. Big thank you too Benjamin Müller
    Was this review helpful?YesNo


    Benjamin Müller provides support for this add-on.

    Vendor support resources


    Find out how this add-on works.


    Community discussions connect you to the vendor and other customers who use this add-on.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.


    Version 3.0.0 Bitbucket Server 4.0.0 - 5.2.2 Released 2015-10-01


    Bitbucket Compatibility


    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Jira Hooks for Bitbucket via search. Results include add-on versions compatible with your Bitbucket instance.
    5. Click Install to download and install your add-on.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Jira Hooks for Bitbucket versions compatible with your instance, you can look through our version history page.

    Similar add-ons