6.10.5 Release Notes

IMPROVEMENTS

• We have added a mechanism for polling the progress of the deployment analysis (diff) phase. This will prevent long-running deployment analyzes from being terminated by proxy timeouts.

• We have improved our deployment progress reporting by adding more steps and messages. This will keep our users informed during time-consuming procedures like workflow scheme migrations.

• We now support comment reactions with emojis introduced in Jira Service Management (JSM) v4.21. With this improvement, users can migrate JSM project configurations including enabled or disabled comment reactions.

• We have added support for project-based swimlanes. Our users will now be able to migrate Jira Software projects with the project-based type of swimlanes configured.

• Compatibility with Jira: Configuration Manager is now compatible with Jira 8.22 and Jira Service Management 4.22.

• Power Admin 2.0.8

• Integrity Check 6.10.5

• SPI 1.7.3

• SPI Tools 1.3.1

RESOLVED

• Fixed a problem where workflow rollback doesn’t revert all changes in a few cases.

• Fixed a problem where snapshot deployment fails when the snapshot includes a filter reference to a project name containing only digits.

• Fixed a problem with the rollback of Agile board columns.

• Reduced the strict requirement for DynamicImport-Package as it didn’t support build tools that may produce manifest with expanded packages.

• Fixed an intermittent “service unavailable” error occurring when trying to cancel an operation.

• Fixed a problem with lost predefined value of a hidden custom fields with options in JSM after deployment.

• Fixed a problem where sprints with the same name are not properly matched causing sprints additions during deployment in case there are multiple identical sprints both in the snapshot and on the target instance.

• Fixed a JSM compatibility issue found on versions [4.20.4, 4.21.0), and 4.21.1.