Manager 10.1.1 Release Notes

June 25, 2020

Review the End of Support Announcements for qTest for important information on upcoming API changes and additional deprecations.

Site Administration enhancement

We have added an option for the Admin to choose whether or not to send the email that contains an activation code to an invited User. By default, the API will not send the email going forward. Some users were finding that the activation link sent through the email was invalid.

Bug fixes

Ticket #	Component	Description
33865, 36445	Test Design	When a user is formatting the test step which has multiple lines and the user selects all the lines and tries to change the font size, an error occurs. The font size is increased for all the lines, but it keeps everything selected other than the first line. Then the user has to select all the lines one more time to change the font size. This has been fixed.
INC0233911	Requirements	When the issue type changes in Jira from "Story" to "Task", the Data Query for "Requirements" module cannot find them, since the user marked the "Jira Issue Type" as null, while the same data displays the correct value in Insights. This has been resolved.
INC0236871	Test Execution	User is creating a Data Query “Date = 26/03/2020”, but when they save it, qTest displays “Date = 25/03/2020". The dB, qTest server, and user are set to GMT +3. This has been fixed.
N/A	Test Execution	On the "Statistics" tab of any module in Test Execution, Users have an option to apply filters. The filters appear to persist in the same browser session regardless of where users navigate. However, after you close out the browser session and return, the filter is no longer applied. Now, the filter will be kept if the user closes the browser or closes all qTest Tab in this browser. However, if the user sets a filter and logs out, then logs in with another account in this qTest Tab (browser), the statistics filter will not be applied to this User.
	Notification Settings	When altering a Requirement, the email notification indicated the change was made by someone else on a different date. This has been fixed.