JIRA Integration December 6, 2019

• 6.11.14
• 8.0.4.

Manager 9.8.8 December 5, 2019

Bug Fixes and Improvements

API Update: In response to the below Module API security fix #35067, we have updated the following API's 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.

1. Module:
   • Get Modules: /api/v3/projects/projectId/modules
   • Get a Module: qtestUrl/api/v3/projects/projectId/modules/moduleId
     • Permission: Requirement and Test Design Tree
2. Test Execution:
   qtestUrl/api/v3/projects/projectId/test-runs/execution-statuses
   Permission: View Test Run
   
   
3. 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
       
       
4. 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 API's listed below will also be affected with this change and users will need "Automation Schedules" Project-level permissions for the associated {projectId}:

1. Create an Automation Agent
   POST /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents
2. Update an Automation Agent
   PUT /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}
3. Delete an Automation Agent
   DEL /api/v3/projects/{projectId}/automation/hosts/{host_server_id}/agents/{agent_server_id}
4. Activate an Automation Agent
   POST
   /api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/activate
5. Deactivate an Automation Agent
   POST /api/v3/projects/{projectId}/automation/hosts/{host_server_Id}/agents/{agent_server_id}/deactivat
6. Update a Job’s Status
   PUT /api/v3/projects/{projectId}/automation/jobs/{job_id}/status

Manager 9.8.7-1 December 2, 2019

Improvement

1. The "JIRA ID" field has been replaced with the "External ID" field. 
2. 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.

Manager 9.8.7 November 21, 2019

Bug Fixes and Improvements

Manager 9.8.6 November 18, 2019

Bug Fixes and Improvements

Manager 9.8.5 November 7, 2019

Enhancement

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" checkbox 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 checkbox 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

Manager 9.8.4-1 October 30, 2019

Bug Fixes and Improvements

Manager 9.8.4 October 29, 2019

API Enhancements

We have enhanced the Manager API's 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 API's to get Test Cases that contain Parameters in the Test Step’s description.

• Get Multiple Test Cases
• Get a Test Case
• Get all Versions of a Test Case
• Get a Version of a Test Case

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 API's

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.

Sample payload:

{
  "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. 

Improvement

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

Manager 9.8.3 October 16, 2019

Bug Fixes and Improvements

Manager 9.8.2 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.