Release Notes
KeyTypeStatusSummaryDescriptionAffects versionsFixversionsJHFB-116ResolvedOption to evaluate all found issue keysIn the past each commit in a push or one commit in a push needs to have only one valid issue key by default. Now you can configure, that all issue keys found in commit messages needs to be valid. Since JHFB-114 Resolved you can explicitly escape issue keys, if the validation should be not done.JHFB-115ResolvedOnly validate against the configured project application linkCurrently it is only possible to evaluate issues against all global configured Jira application links. Now it is possible to check issues only against configured project links.JHFB-114ResolvedEscape issues with configurable escape characterIssues found in the commit message, which will be escaped with a special character will not be evaluated. The escape character can be configured.
Known Bugs
KeyTypeStatusSummaryDescriptionAffects versionsFixversionsJHFB-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-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 prevented