Key T Status Summary Description Affected Version/s Fix Version/s
JHFB-132 Bug Closed Fixing the vulnerability CVE-2021-27568

Please 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.

5.2.0, 5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.5.0, 5.6.0, 5.6.1, 5.7.0, 5.7.1 5.7.2
JHFB-131 Bug Closed Option 'Skip commits' could not be enabled

The push and merge option 'Skip commits' can be enabled. The check box for 'Skip commits' doesn't react to mouse clicks.

5.1.0, 5.2.0, 5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.5.0, 5.6.0, 5.6.1, 5.7.0, 5.7.1 5.7.2
JHFB-130 Bug Closed Pull Request target branch enablement is not working

The regex regarding the target branch enablement was not working as expected. Also with a given regular expression all branches has been checked.

5.7.0 5.7.1
JHFB-127 Bug Closed Moved tickets has not been handled correctly

The 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.

5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.1.0, 5.0.7, 5.2.0, 5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.5.0, 5.6.0, 5.6.1 5.7.0
JHFB-121 Bug Resolved Push settings has not been validated

The settings for the push checks were not validated. Now incorrect combinations of the settings are detected and prevented

5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.5.0 5.6.0
JHFB-120 Bug Resolved The "online branch creation" could not be disabled

The option was permanently switched on. In the settings the checkbox could be disabled, but it was set again the next time the program was loaded

5.5.0 5.6.0
JHFB-113 Bug Closed Configured project application links not respected

All 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.

5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.1.0, 5.0.7, 5.2.0, 5.3.0, 5.3.1 5.3.2
JHFB-112 Bug Closed ​"Skip commit based on keyword" configuration has no affect to local commit checks

The option to skip the evaluation based on special keywords in the commit message, was not enabled for local commit checks.

5.3.0 5.3.1
JHFB-111 Bug Closed All checks are working with less then 50 issues only

The 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.

4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.2.5, 4.2.6, 4.2.7, 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 4.4.0, 5.1.0, 5.0.7, 4.0.7, 5.2.0 5.3.0
JHFB-108 Bug Resolved Multiple Jira application links breaks validation of hook configuration

The 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"

5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6 5.0.7
JHFB-104 Bug Resolved Push validation checks all configured Jira Servers

A 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.

5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6 5.0.7
JHFB-103 Bug Resolved Option "Each branch name should contain a valid issue key" needs mandatory text field option

After enabling the option "Each branch name should contain a valid issue key" the option "Enable the hook only for configured branches" become mandatory.

5.0.6 5.0.7
JHFB-96 Bug Closed JQL check will be performed without issue key

The 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.

5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5 5.0.6
JHFB-88 Bug Closed Merge message is disabled, but will be checked

In some cases the merge messages will be checked, but the merge check is disabled.

5.0.0, 5.0.1, 5.0.2, 5.0.3 5.0.4
JHFB-85 Bug Closed IllegalStateException regarding custom fields

During pull, merge and branch creation there occur a IllegalStateException. As result the action will be blocked.

5.0.0, 5.0.1, 5.0.2 5.0.3
JHFB-82 Bug Closed The branch creation from Jira is broken

If the hook is not enabled and not configured, it could be that the hook still blocks the branch creation with Exception as error message

5.0.0, 5.0.1 5.0.2
JHFB-81 Bug Closed Hook configuration can not be saved, if no application link is available

If no hook configuration is enabled, the hook configuration can not be saved.

5.0.0 5.0.1
JHFB-80 Bug Closed Duplicate error message during branch creation validation

If a user tries to create a branch from Jira, all failed checks will be reported twice.

5.0.0 5.0.1
JHFB-79 Bug Closed Branch name will not be evaluated

If 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.

4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.2.5, 4.2.6, 4.2.7 5.0.0
JHFB-71 Bug Closed Migration: Upgrade merge settings has been disabled

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

https://develop-and-consult.atlassian.net/wiki/x/AQD9H

4.2.7
Showing 20 out of 35 issues