Known Bugs
| Key | T | P | Status | Summary | Description | Affected Versions | Fix Versions |
|---|---|---|---|---|---|---|---|
| SCFB-51 |
|
|
Closed | Fixing the vulnerability CVE-2023-1370 |
Jira actions are performed with a JSON payload. In this case the libray "net.minidev-json-smart", which is affected by CVE-2023-1370, was used to create this payload. However, the critical functionality had no negative impact on the add-on. Nevertheless, the library was updated. |
1.2.0, 2.2.0, 1.2.1, 2.2.1, 2.3.0, 3.0.0, 3.1.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 4.0.0 | 4.0.1 |
| SCFB-47 |
|
|
Closed | Fixing the vulnerability CVE-2021-27568 |
Please update to the version 3.0.5. Because this version contains the vulnerability CVE-2021-27568 . This vulnerability occurs because the library json-smart-1.1.1.jar which is shipped and used with this version. |
0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 1.0.0, 2.0.0, 2.1.0, 1.1.0, 1.2.0, 2.2.0, 1.2.1, 2.2.1, 2.3.0, 3.0.0, 3.1.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4 | 3.0.5 |
| SCFB-42 |
|
|
Closed | Hook is not working if the header option as not been set. |
If the option "Enable or disable the Jira comment header" is initially not set, the hook runs into a exception case an do not continue the processing of the smart actions. |
3.0.0, 3.0.1, 3.0.2 | 3.0.3 |
| SCFB-41 |
|
|
Resolved | Worklog will not be created |
Even the worklog action is enabled ("Work logs - add work logs to issues"), a worklog will not be created. A worklog will only be created if the option is enabled in combination with a further option ("Time tracking - return the time tracking values") |
3.0.0, 3.0.1 | 3.0.2 |
| SCFB-39 |
|
|
Resolved | A reviewer action was not possible together with a pull request creation |
In some situations it was not possible to create a pull request and add a reviewer in the same commit message. Example: #pull master #reviewer @tester
|
2.0.0, 2.1.0, 2.2.0, 2.2.1, 2.3.0 | 3.0.0 |
| SCFB-29 |
|
|
Closed | Some general refactorings to improve the performance |
The code has been refactored to improve the general workflow. The results is a more performant way to parse and execute commands. |
1.0.0, 2.0.0, 2.1.0, 1.1.0, 1.2.0, 2.2.0 | 1.2.1, 2.2.1 |
| SCFB-28 |
|
|
Closed | No empty tags and branches are handled by the plugin |
The hook does not longer handle empty branches, notes and tags. This will improve the performance is some cases (factor 10) |
1.0.0, 2.0.0, 2.1.0, 1.1.0, 1.2.0, 2.2.0 | 1.2.1, 2.2.1 |
| SCFB-27 |
|
|
Closed | Improved the handling of magic keywords |
Keywords are now better organized to reduce the traffic to Jira |
1.0.0, 2.0.0, 2.1.0, 1.1.0, 1.2.0, 2.2.0 | 1.2.1, 2.2.1 |
| SCFB-14 |
|
|
Closed | Confusing licensing error message |
The error message does not contain the plugin name, if no valid license is available. |
1.0.0, 2.0.0 | 2.1.0, 1.1.0 |
| SCFB-6 |
|
|
Resolved | The keyword @stash is used to create a Pull-Request comment |
The plugin has been developed for Stash. Thats the reason, why magic keywords in the commit messages are based on the name @stash. Since the renaming to Bitbucket, the magic comments needs to be renamed also. Both keywords should be supported. Since the version 3.0.0 in addition also @bb is possible to create comments |
1.0.0, 2.0.0, 2.1.0, 1.1.0, 1.2.0, 2.2.0, 2.3.0 | 3.0.0 |