Jira Hooks for Bitbucket
Before you will commit, push or merge changes you need to check the corresponding Jira issue. Establish and protect your workflow
The merge, commit 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".
Commit & Push Protection
The hook will check, if commits and the related issues are as expected (at commit time and push time). Is the commit or the issue not as expected (e.g. no valid issue) the commit and/or the push will be rejected.
Jira Hooks for Bitbucket integrates 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.
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.
See Confluence Hooks for Bitbucket improve you workflow with Confluence hooks :)
Privacy and security
The given issue does not exist in Jira