6.11.2 Release Notes

12 August 2022

Appfire team is happy to announce the release of Configuration Manager for Jira 6.11.2!

Upgrading to Configuration Manager for Jira 6.11.2 is free for all customers.

Highlights

• Improved project selection when deploying a single project snapshot in Merge Project mode

• Improved error messages for failing snapshot creation, integrity check, initial analysis, and deployment

• Improved the Audit Log by adding a new entry for issues containing custom field values for old contexts

• Performance improvements

• Bug fixes

Get the latest version

Updates and Resolved Issues

IMPROVEMENTS

• We have improved project selection when deploying a single project snapshot in Merge Project mode. Now, our users will see projects with their name and key in the Select Target Project dropdown. The project’s key ensures that users select precisely the project on which they want to apply the snapshot configuration.

• We have improved our error messages shown for failing snapshot creation, integrity check, initial analysis and deployment. Now you will know when your snapshot could not be created, checked, or deployed because CMJ is running the same process for another snapshot at the same time.

• We have improved the Audit Log by adding a new entry. Now, users will see a warning entry in the Audit Log when they are creating or deploying snapshots containing issues with custom field values for old contexts.

• Performance improvements. We’ve made snapshot creation and deployment run even faster than before.

• Power Admin 2.0.13

• Integrity Check 6.11.2

RESOLVED

• Fixed a problem where if snapshot creation fails, the snapshot could still be downloaded as a broken file that could not be opened.

• Fixed a problem where during deployment adding new sprints could throw an error because of a missing board.

• Fixed a problem where pressing the “Enter” key while creating/recreating a snapshot refreshes the page and makes users start creating the snapshot from scratch.

• Fixed a problem where the Audit Log’s messages did not show the issues referring to a missing user.