Version 5.3.0
Release Notes
| Key | T | Status | Summary | Description | Affected Versions | Fix Versions |
|---|---|---|---|---|---|---|
| JHFB-110 |
|
Closed | Support of local commit checks |
Now it is possible to check a commit messages not only at push time. Since this version the commit message can be evaluated also at commit time. We have introduced a new Rest-API endpoint, which enables you to check a commit message at any time in your process. For example in a Git hook, which is probably the major task of this API. Check our How-To: How to configure a local commit hook? In this How-To we have provided a commit-msg hook based on Python3, which will use this Rest-API to evaluate a commit message during runtime. |
5.3.0 | |
| JHFB-111 |
|
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 |
Known Bugs
| Key | T | Status | Summary | Description | Affected Versions | Fix Versions |
|---|---|---|---|---|---|---|
| JHFB-132 |
|
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 |
|
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-127 |
|
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 |
|
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-113 |
|
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 |
|
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 |