Manager 9.8.2+ Release Notes

Jira Integration

We are excited to announce the release of two new Jira Server and Jira Data Center add-ons to the Atlassian Marketplace.

Add-on Versions:

6.11.14
8.0.4.

These new add-ons support qTest 9.7.1+ OnPremise, as well as qTest OnDemand customers that are using self-signed certificates.

However, if you are using an outbound proxy for Jira you cannot use a self-signed certificate with these new add-ons, and you are required to perform additional configuration steps.

Read the Jira Server/DC Add-on 6.11.14 and 8.0.4 for additional configuration information that is required.

Manager 9.8.8 Release Notes

December 10, 2019

API Update

In response to the below Module API security fix #35067, we have updated the following APIs which enhances security to view/retrieve responses from Projects and requires users to have appropriate Project level-permissions.

Therefore, from 9.8.8 and going forward, users will require Project-level permissions for any API and UI actions unless the API is specifically at the Site-level and does not target a specific Project.

Module:
- Get Modules: /api/v3/projects/projectId/modules
- Get a Module: qtestUrl/api/v3/projects/projectId/modules/moduleId
  - Permission: Requirement and Test Design Tree
Test Execution:
- qtestUrl/api/v3/projects/projectId/test-runs/execution-statuses
  - Permission: View Test Run
Link Objects:
- Remove link objects - Success with link between build and requirements
- qtestUrl/api/v3/projects/projectId/builds/newBuildId1/link?type=requirements
  
  Permission Notes:
  - Build: support requirement
    - Permission: Edit Release\Build + View Requirements
  - Release: support requirement
    - Permission: Edit Release/Build + View Requirements
  - Requirement: support Test Case
    - Permission: Edit Requirement + View Test Cases
  - Test Logs: support Defects
    - Permission: Edit Test Run
  - Test Step Logs: Defects
    - Permission: Edit Test Run
Custom fields:
- Get fields: /api/v3/projects/projectId/settings/{objectType}/fields
  - Create custom field: ( release / build / requirement / test case / test suite / test run / defect/api/v3/projects/projectId/settings/objectType/fields
  - Update system field: /api/v3/projects/projectId/settings/defects/system-fields/6421
    - Permission: Manage Field Settings

Additionally, the Automation Integration APIs listed below will also be affected with this change and users will need "Automation Schedules" Project-level permissions for the associated {projectId}:

Create an Automation Agent
- POST /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents
Update an Automation Agent
- PUT /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}
Delete an Automation Agent
- DEL /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}
Activate an Automation Agent
- POST/api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/activate
Deactivate an Automation Agent
- POST /api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/deactivate
Update a Job’s Status
- PUT /api/v3/projects/{projectId}/automation/jobs/{job_id}/status

Bug Fixes and Improvements

Ticket #	Component	Description
33090	Test Execution	When attempting to view a Test Cycle that included over 100,000 Test Runs, some users experienced longer than expected load times of the Test Execution page. This is now fixed.
35067	Security: APIs	Previously, when using the Module API, some users were able to view/retrieve responses from Projects without appropriate permissions. This is now resolved. The following message is the expected result: "User needs to be assigned to project to perform this action!"

Ticket #

Component

Description

33090

Test Execution

When attempting to view a Test Cycle that included over 100,000 Test Runs, some users experienced longer than expected load times of the Test Execution page. This is now fixed.

35067

Security: APIs

Previously, when using the Module API, some users were able to view/retrieve responses from Projects without appropriate permissions. This is now resolved.

The following message is the expected result: "User needs to be assigned to project to perform this action!"

Manager 9.8.7-1 Release Notes

December 2, 2019

Data Query with Jira fields

In response to PIR-154, the "Data Query with Jira fields" enhancement that was released with Manager 9.8 has been modified to reduce the number of database connections. The following changes are applied to the Requirement Data Query:

The "Jira ID" field has been replaced with the "External ID" field.
In the Criteria drop-down, the "Jira Issue Type" field has been replaced with the "External Object Type" field. However, users will still see “Jira Issue Type” in Customize View, Query Results grid and Export.

If there are any saved queries that used the "Jira ID" or "Jira Issue Type" fields before, they will be changed automatically without any effect on the query result. The user will also see "External ID" and "External Object Type" in Customize View, Query Results grid, and Export.

Manager 9.8.7 Release Notes

November 21, 2019

Bug Fixes and Improvements

Ticket #	Component	Description
NA	Test Execution	When creating a Test Run with historical parameters, users were receiving a 400 bad request error. This has been fixed.

Manager 9.8.6 Release Notes

November 18, 2019

Bug Fixes and Improvements

Ticket #	Component	Description
33087	Rally Integration	When submitting Defects to Rally, the autofill function was not working. After the Defect was submitted successfully, users were not redirected to qTest. This is now resolved. The Chrome extension includes an "active tab" permission. When users click to submit a new defect to Rally, then a new browser tab/window will be open with the defect submission form of Rally. While the new tab/window is quickly loading with the auto-fill, users should not open or switch to another tab/window, or else the autofill will fail.
34870	Jira Integration	Atlassian API changes affected the Jira integration and some users could not create new defects from qTest to Jira nor could they save the Jira connection. Error messages were received when saving the connection "Connection failed. Permissions queries data is required". Issue types linked to Jira were not visible from the Integration Settings page. This is resolved.

Manager 9.8.5 Release Notes

November 7, 2019

Ability to Display the Password for Project Integration Connections

Project Admins now have the ability to view the password/token that is associated with integrated Projects. This enhancement is associated with an upcoming release for qTest Scenario, where the password/token is needed. A "Show Password" check box has been added to the Add Connection dialogue and is not selected by default. Once selected, Project Admins can view and copy/paste the password or token. When closing the Add Connection dialogue, the check box resets to the default and the password/token will be hidden again.

This enhancement is available for the following integration connections:

Jira
VersionOne
Rally
Bugzilla
FogBugz

Bug Fixes and Improvements

Ticket #	Component	Description
30481	Licenses page	On the Administration>Licenses page, the License Information section displays the date the qTest License is due to Expire. Previously, the field was labeled as "Expired On," which was past tense. We have updated the field name to "Expires On" for future tense grammatical representation.
33813	Test Execution	After adding Test Cases from the ADD button in the Test Execution Tab, users needed to refresh the page in order to select the Test Cases to edit them. This is now resolved.
34442	Notifications	When saving a notification for Requirement changes, some users reported receiving an oops error. This is now fixed.

Manager 9.8.4-1 Release Notes

October 30, 2019

Bug Fixes and Improvements

Ticket #	Component	Description
34361	Pulse Access	Users were unable to access Pulse from the 9-box due to a change in the access token used for authentication to the app. This is now resolved.

Manager 9.8.4 Release Notes

October 29, 2019

We have enhanced the Manager APIs to allow our users to create Test Cases and Test Runs with Parameters in the Test Case Steps.

Test Case APIs

Create a Test Case : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when creating a Test Case.

Parameters will be automatically added to the current Project.
The provided parameter_identifier must exist in the Parameters application to work.
The allowed input uses the [~<parameter_identifier>] format.
Potential Error message: return code of 404 with list of all invalid parameters. Ex: "parameter1, parameter2 not found"

Update a Test Case : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when updating a Test Case.

Parameters will be automatically added to the current Project.
The provided parameter_identifier must exist in the Parameters application to work.
The allowed input uses the [~<parameter_identifier>] format.
Potential Error message: return code of 404 with list of all invalid parameters. Ex: "parameter1, parameter2 not found"

You can use the following GET Test Case APIs to get Test Cases that contain Parameters in the Test Step’s description.

Test Step APIs

Create a Test Step : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when creating a Test Step.

Parameters will be automatically added to the current Project.
The provided parameter_identifier must exist in the Parameters application to work.
The allowed input uses the [~<parameter_identifier>] format.
Potential Error message: return code of 404 with a list of all invalid parameters. Ex: "parameter1, parameter2 not found"

Update a Test Step : we now support the ability to input one or multiple parameter identifier(s) to each test_steps.description property when updating a Test Step.

Parameters will be automatically added to the current Project.
The provided parameter_identifier must exist in the Parameters application to work.
The allowed input uses the [~<parameter_identifier>] format.
Potential Error message: return code of 404 with a list of all invalid parameters. Ex: "parameter1, parameter2 not found"

Test Run APIs

Create a Test Run : we now support the ability to Create Test Runs via randomizing, manually and dataset via API. You can use the Gets a Batch Test Logs Submission jobs state API to track the "Create Test Runs" job.

Randomized: To create multiple Test Runs with parameter values under root or a container (Release, Test Cycle or Test Suite). The maximum number of test runs can be created depending on the combined type.
Manual: To create multiple Test Runs with parameter values under root or a container (Release, Test Cycle or Test Suite). The maximum number of test runs that can be created is 100.
Dataset: To create multiple Test Runs with parameter values under root or a container (Release, Test Cycle or Test Suite). The number of test runs that can be created depend on number_of_rows property and it should not be more than 100.

{
  "name": "Test Run Name",  
  "properties": [
    {
     "field_id": 123,  
     "field_value": "123"
    }
  ], 
  "test_case": {
    "id": 123,
    "test_case_version_id": 111
  },
  "dataset_id": 123, 
  "from_row": 10 ,
  "number_of_rows": 5
}

Update a Test Run : we now support the ability to update parameter values to an existing Test Run step.

Return updated test run information with updated test case steps. Parameter values set/updated to test run.

Sample Payload:

                "assign_parameter_values": [
	    {  "step_id": 233045404,
	       "parameter_values": ["parameter_value_name"]
	    },
	    {   "step_id": 233045402,
		"parameter_values": ["parameter_value_name", "parameter_value_name"]
	    },
	    {   "step_id": 233045430,
		"parameter_values": ["parameter_value_name"]
	    }
]

"assign_parameter_values": if the provided assign_parameter_values property AND test run is linking to a test case version AND the test run has an executed test log for this test case version then we DO NOT allow to set/update parameter values.
"step_id": belongs to the specified test case/test case version.
"parameter_values": belongs to the specified parameters in the above test case step.

The Add Project Users dialog is enhanced for greater flexibility when managing your Project users. Project Admins, with the Edit Project Settings permission, can now Search for, Apply All, Add and Remove users when maintaining Projects. This enhancement is especially useful for organizations with many qTest users associated to one Project .

Additionally, a new Search Users field is available above the User List on the User Management screen. This provides a quicker approach for searching individual users when managing their Project permissions.

For more information on maintaining your Users' Projects, and Profiles read this article.

Test Step Attachment Improvement

While performing a Test Run, you can now save a new Test Step that only contains an attachment.

Manager 9.8.3 Release Notes

October 17, 2019

Bug Fixes and Improvements

Ticket #	Component	Description
30612	Jira Integration	When selecting the Retrieve Jira Data button on the Jira Integration > Requirements section, the manual sync would stall for some Jira Server users. This is now resolved.
PIR-148	Jira Integration	The Jira integration and qTest synchronization were not performing properly for many users. This is fixed.
33411, 33598, 33406, 33407, 33416	Email Notification	Many users received duplicate email notifications stating they had been assigned to a Project, or assigned to a Project as an Admin, when the users were previously assigned. This issue is now resolved.
33094	Data Query	The Data Query for Jira fields were not updating as expected. This issue was related to the data sync with Jira integration. This is now fixed.

Manager 9.8.2 Release Notes

October 7, 2019

Bug Fixes and Improvements

The Jira Requirements integration was not auto-linking properly in qTest. This is now fixed. Previously, some users experienced an issue with Jira requirements already synced to qTest, when changes were made to the Fix Version/Sprint of a User Story in Jira.

Ticket	Component	Description
23921	TestPad	Notes added to an execution log, displayed the qTest servers timezone instead of the timezone associated with the PC. The time stamp displayed in the note was UTC. This is now fixed.
31327, 31908, 31373, 33175, 32821	Test Execution	Exported reports for Test Execution would not display all headers for the selected columns of the "Export Test Run Detail" feature. Additionally, after exporting, some of the previously selected fields would no longer be visible for selection again. This is resolved.
32588, 33264	Test Execution	Some users encountered an issue when attempting to export Test Run Details when a custom field was removed from the Test Run. This placed a null value in the selected columns for the report, which returned an error. This is now resolved.
33222	Notifications	Previously, notification settings were not saving properly when activating/deactivating. This is now fixed.