KeyTypeStatusSummaryDescriptionAffects versionsFixversionsJHFB-137ClosedBroken validation of the exception group settingsValidation does not allow to enter more than one exception group separated by a commaJHFB-132ClosedFixing the vulnerability CVE-2021-27568Please update to the version 5.7.2. Because this version contains the vulnerability CVE-2021-27568 . This vulnerability occurs because the library json-smart-1.1.1.jar which is shipped with this version. This library is NOT used by our add-on, but it is shipped with our add-on.JHFB-131ClosedOption 'Skip commits' could not be enabledThe push and merge option 'Skip commits' can be enabled. The check box for 'Skip commits' doesn't react to mouse clicks.JHFB-130ClosedPull Request target branch enablement is not workingThe regex regarding the target branch enablement was not working as expected. Also with a given regular expression all branches has been checked. JHFB-127ClosedMoved tickets has not been handled correctlyThe hook has not detected, that issue has been moved. As soon the issues has been moved and the old issue key has been used in branch names or commit messages, then the hook has rejected merges and pushes. Now the hook handle this kind of issues correctly.JHFB-121ResolvedPush settings has not been validatedThe settings for the push checks were not validated. Now incorrect combinations of the settings are detected and preventedJHFB-120ResolvedThe "online branch creation" could not be disabledThe option was permanently switched on. In the settings the checkbox could be disabled, but it was set again the next time the program was loadedJHFB-113ClosedConfigured project application links not respectedAll application links were always used to check issues. The project-specific application links were not considered. As a result, in the worst case all users had to have rights for all Jira instances. Now the configured project links are used first and only if the issues are not found in them, the other Jira instances are contacted via global application links.JHFB-112Closed"Skip commit based on keyword" configuration has no affect to local commit checksThe option to skip the evaluation based on special keywords in the commit message, was not enabled for local commit checks.JHFB-111ClosedAll checks are working with less then 50 issues onlyThe results of a Jira rest call is limited to 50 entries by default. In the case more than 50 issues will be detected via the rest api call, the issues 51 - x will be evaluated as error.JHFB-108ResolvedMultiple Jira application links breaks validation of hook configurationThe hook configuration validation reports an error, if there are multiple Jira instances are configured and the user does not have valid credentials to all of them. In this version the user can disable the validation of all Jira instances via a checkbox. As result the validation reports an error only, if no valid Jira application link has been found. This behaviour can be enabled with the option: "If selected, not all application links needs to be reachable/accessible"JHFB-104ResolvedPush validation checks all configured Jira ServersA Bitbucket push will be validated against all configured Jira instances. Maybe not all developers has valid credentials to all Jira Instances. In this release the "Primary Server" will be evaluated first, if the issue has been found, no further evaluation will be done.JHFB-103ResolvedOption "Each branch name should contain a valid issue key" needs mandatory text field optionAfter enabling the option "Each branch name should contain a valid issue key" the option "Enable the hook only for configured branches" become mandatory.JHFB-96ClosedJQL check will be performed without issue keyThe JQL check will be performed, if no issue key is given. This will raise errors, if users will push empty branches without issue keys in the branch name.JHFB-88ClosedMerge message is disabled, but will be checkedIn some cases the merge messages will be checked, but the merge check is disabled. JHFB-85ClosedIllegalStateException regarding custom fieldsDuring pull, merge and branch creation there occur a IllegalStateException. As result the action will be blocked.JHFB-82ClosedThe branch creation from Jira is brokenIf the hook is not enabled and not configured, it could be that the hook still blocks the branch creation with Exception as error messageJHFB-81ClosedHook configuration can not be saved, if no application link is availableIf no hook configuration is enabled, the hook configuration can not be saved.JHFB-80ClosedDuplicate error message during branch creation validationIf a user tries to create a branch from Jira, all failed checks will be reported twice.JHFB-79ClosedBranch name will not be evaluatedIf a empty branch will be committed, the branch name will not be evaluated. The branch name will only be evaluated, if the branch contains commits.JHFB-71ClosedMigration: Upgrade merge settings has been disabledDue 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 https://develop-and-consult.atlassian.net/wiki/x/AQD9HJHFB-68ClosedRollback after upgrade task has done the migrationAfter the upgrade task has done the migration of the merge hook configuration, the migration will be rolled back if the legacy settings have invalid entries. As result the hook settings are. not merged. "Transaction rolled back because it has been marked as rollback-only"JHFB-66ClosedMigration of 3.x settings not always successfulDuring the update of the add-on from version 3.x to 4.x the merge settings are lost. In the last release we have introduced a migration of the data, but this migration does not always works as expected. As result the settings are not taken. In this release the migration will be done based on a more stable mechanism. 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.JHFB-64ClosedMerge Check' settings are lost after upgrade During the update of the add-on from version 3.x to 4.x the merge settings are lost. JHFB-52ClosedCheck conditions has no effectThe check enablement settings "Enable the hook only for configured branches" and "Enable exception handling for users" in the push settings has no effect, if a branch will be created via UI.JHFB-50ClosedCreate branches via Bitbucket UI results in ExceptionThe creation of a new branch is not possible from the Bitbucket UI, if the hook is not configured/enabled. The creation of a branch will result in a exception. Possible reasons: If the hook has never been configured The settings will be inherit but the project hook has never been configured A fork will be created an the hook is not enabled JHFB-49ClosedOnly admins are able to create branches via Bitbucket UIIf a user has write permissions only without admin rights, the UI rejected the branch creation based on permission issues. But also non admin users should be able to create branches.JHFB-48ClosedCreation of a branch fails via Bitbucket UIIf issue key checks are enabled, it was not possible to create a branch via the Bitbucket UI.JHFB-47ClosedBranch check evaluates also tag nameIf a issue check is enabled based on branches and a new branch with new commits will be pushed together with a tag, the tag will be checked also based on the naming convention. As result the tag name should have also a valid issue key.JHFB-39ClosedConfusing error message in JQL checkIf there is a issue key, which does not exist in Jira and a JQL check is configured, then the JQL check fails. This is correct, but the error message is confusing and does not point out the correct problem.JHFB-32ClosedMerge Hook configuration validation brokenThe validation of the merge hook configuration page was not enabled. So it was possible to set a invalid merge configuration.JHFB-26ClosedConfusing licensing error message The error message does not contain the plugin name, if no valid license is available.JHFB-24ClosedMerge and Push validation broken based on Issue Key RegEx The issue key validation was broken based on the regular expression for issue keys. If the field is empty (not NULL -> empty string), the empty string will be used as issue key regex. As result each push and each merge will be rejected with an exception as error message.JHFB-22ClosedEmpty Push is not possibleA push without change-set will not be accepted, because it contains no change-set with a valid issue-key. As result the a push, which will just delete/add tags/branches will be rejected.JHFB-18ClosedEmpty hook configuration pageSince the version 5.2.x the hook configuration was broken. It was no longer possible to configure the hooks. This has been solved with this hotfix.JHFB-11ClosedIndexer module is disabledAfter the update to the latest API changes of Atlassian the indexer does no longer working.