Klaros-Testmanagement 5.4.5 released - Klaros Test Management - Forum - Klaros Test Management
Klaros-Testmanagement 5.4.5 released
Torsten Stolpmann, modified 1 Year ago.
Klaros-Testmanagement 5.4.5 released
Jedi Council Member Posts: 759 Join Date: 2/12/09 Recent Posts
We are happy to announce the availability of Klaros-Testmanagement 5.4.5.
This maintenance release compensates for token size changes introduced in the JIRA Cloud API and add several minor bug fixes and improvements.
Overall this release contains 3 improvements and 2 bug fixes. Existing users are encouraged to upgrade to this version.
Release Notes Version 5.4.5 (15.02.2023)
Improvements
[KLAROS-5148] - Improve error handling of missing background synchronization credentials for Redmine issue trackers
[KLAROS-5149] - Raise password/token size limit for background sync of issue and requirements management systems to reflect recent token size changes in JIRA Cloud
[KLAROS-5150] - Purging an issue management system should only be allowed when it is no longer linked to any project
Bug Fixes
[KLAROS-5143] - Potential race condition when two users are simultaneously executing an identical test step for the first time
[KLAROS-5146] - When importing JUnit test results the test suite result may not be correctly identified
This maintenance release compensates for token size changes introduced in the JIRA Cloud API and add several minor bug fixes and improvements.
Overall this release contains 3 improvements and 2 bug fixes. Existing users are encouraged to upgrade to this version.
Release Notes Version 5.4.5 (15.02.2023)
Improvements
[KLAROS-5148] - Improve error handling of missing background synchronization credentials for Redmine issue trackers
[KLAROS-5149] - Raise password/token size limit for background sync of issue and requirements management systems to reflect recent token size changes in JIRA Cloud
[KLAROS-5150] - Purging an issue management system should only be allowed when it is no longer linked to any project
Bug Fixes
[KLAROS-5143] - Potential race condition when two users are simultaneously executing an identical test step for the first time
[KLAROS-5146] - When importing JUnit test results the test suite result may not be correctly identified