6.10.2 Release Notes

21 September 2021

Botron team is happy to announce the release of Configuration Manager for Jira 6.10.2!

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

Highlights

• Anonymized analytics data is captured

• Audit log entries are included in the Jira log

• Violations due to SPI errors are warnings

• Quick fix for removing invalid permissions

• Improvements to workflow transition participant matching

• Performance improvements to Selective Merge’s analyze operation

• Compatibility with Jira 8.19 and Jira Service Management 4.19

• Bug fixes

Get the latest version

Updates and Resolved Issues

FEATURES

• Analytics data: Configuration Manager captures anonymized analytics data to allow improvements in future releases.

Learn more

IMPROVEMENTS

• Configuration Manager's Audit Log events are now logged in the Jira log as well when debug logging is enabled. The extended Jira log will improve customer support, mainly when a Jira support zip is provided but no CMJ audit logs are present.

• Now, errors that happen in SPI implementations are reported with warning severity instead of error in Integrity Check for Jira. These SPI errors are treated as warnings when creating a snapshot, i.e. they do not prevent the creation of snapshots.

• New quick fix: We’ve added a new quick fix to remove invalid dashboard and filter permissions.

• We’ve improved the workflow transition participant matching to avoid unnecessary additional changes being reported in the diff.

• We’ve introduced performance improvements to Selective Merge’s analyze operation.

• Compatibility with Jira: Configuration Manager is now compatible with Jira 8.19 and Jira Service Management 4.19.

• Power Admin 2.0.5

• Integrity Check 6.10.2

RESOLVED

• Fixed a problem where there is a missing violation in the system scope integrity check about missing user referenced from a custom field context.

• Fixed a problem where custom fields with no references in the exported project were added to the snapshot.

• Fixed a problem where the deployment could lead to two global custom field contexts for a single field.

• Fixed a problem where the snapshot creation fails because of issue security levels set to a non-existent ID.

• Fixed a problem where rollback doesn't clean all custom field context changes.

• Fixed a problem where wrong deployment and re-indexing time was shown on the last deployment wizard step.