qTest Manager 9.0 OnPremise Release Notes - Feb 26, 2018

Installation/Deployment Packages

Linux Docker deployment packages

  • One Docker deployment package to deploy qTest Manager, qTest Sessions, qTest Insights, qTest Parameters, qTest Launch

Linux non-Docker installation/upgrade package

  • One package for installing qTest Manager, qTest Sessions, qTest Insights and qTest Parameters (no new update to Parameters)

Windows installation packages

  • One package for installing qTest Manager, qTest Sessions, qTest Insights and qTest Parameters (no new update to Parameters)

Plugin/Tool Updates

  • Please update your JIRA Server plugin (qTest for Jira Server - Test Management) to our latest version (v6.11.7)

New Features

Release Integration with Jira Sprints or Fix Versions

  • This feature allows you to automatically create Sprints and/or Fix Versions from your Jira projects to Manager. Check out this article for more details: Import and Use Releases from Jira
  • Requirements that are part of the scope for these Sprints and/or Fix Versions are also auto-populated to Manager
    • Only Jira issues which are configured to be imported to Manager as Requirements will be linked to the corresponding synced Releases
    • You have the option to link standalone Requirements with JIRA Releases in Manager’s Test Plan. These relationships will not be impacted by any updates from Jira Releases
  • Similar to configuring Jira Requirements Integration, you can enable Release Integration and then select Sprints and/or Fix Version from your JIRA projects to be imported into your Manager project
    • For each configured Sprint or Fix Version, there are options to specify which Sprints or Fix Versions you wish you automatically create in Manager. For example:
      • Sprints:
        • Active Sprints
        • Future Sprints
        • Completed Sprints
      • Fix Versions:
        • Unreleased
        • Released


  • Any updates in Jira Fix Version or Sprints will be updated in real time to Manager. For example, Start and End Dates, Fix Version Description, and Sprint Goal
  • Any updates in Manager will not be synchronized back to Jira
  • It is highly recommended that you update the Fix Version or Sprint scope in Jira instead of in Manager since updates in Manager are not updated to Jira
    • When adding Requirements to a Jira Release, only Requirements created internally in Manager are included in the tree. Requirements from Jira are excluded
    • When searching for Requirements to add them to a Jira Release scope, Jira Requirements are included in the search result but you are not able to add them to the scope of these Releases
    • You are not able to remove Jira Requirements from the scope of Jira Releases



Ability to customize view of Defect Summary tab in Release, Test Cycle, Test Suite pages, and Defect tab in Test Run page

  • You are able to add more fields (qTest or JIRA fields) to the grid, and drag-drop columns to reorder them. This Defect Summary view is your personal view (does not impact other users) and the customized view will be retained for your next login session


  • NOTE: If there are any field settings updates in JIRA but you have not seen the updates in qTest Manager, the Project Admin should Refresh Field Settings in the Defect Configuration dialog of Integration Settings. Refreshing these defect fields will allow you to view the latest field settings from JIRA (e.g. Updated defect field names, new defect custom fields or values)


Ability to Add Requirement to Scope of multiple Releases and Builds

  • In the past, if a Requirement from Release A was added to Release B, the Requirement was removed from the Release A scope (and part of Release B scope only)
  • Now, if a Requirement from Release A was added to Release B, the Requirement will remain as part of both Release A and Release B scopes
  • If you prefer to completely move the Requirement to Release B only, you can manually remove it from the original Release A scope

Ability to Add Test Runs from Release or Build Scope

  • In Add Test Runs dialog, a new tab named Test Plan is added. You can select Releases, Builds or individual Requirements under their scope to create Test Runs. By doing so, you will add any Test Cases that were linked to the selected Requirement(s) as Test Runs
  • Requirements without associated Test Cases or Target Release/Build will not show up on the tree
  • If you wish to add test runs based on a more complex requirements query, you can use the existing Requirements tab in the Add Test Runs dialog


Ability to link Requirements to Test Cases from Release or Build scope

  • Similar to the above enhancement, you can select Releases, Builds or individual Requirements from their scope when linking Requirements to a Test Case


  • Ability to set a fìeld as required without selecting a default value
    • The system will no longer auto-select a default value for picklist fields that are marked as “required”
    • In the Field Settings panel, the Project Admin can now deselect the default value of existing required fields
  • Improve the display of History tab in Test Suite and Test Run pages
    • Instead of clicking on Content Change link to view the old value vs new value of a field, they are shown directly on the History grid
  • Display consistent Test Run order within a Test Suite (Test Run order in the left panel tree matches the order in the Test Run grid)
    • Whenever Test Runs are reordered in the grid, the order in the tree is automatically updated in real-time
    • However, when Test Runs are reordered in the left panel tree, the Test Run order in the grid will not auto-refresh. To streamline this process, there is a notification bubble will prompt you to manually reload the page if data was changed
  • Shared Test Cases’ information is included in the Test Run grid in Release, Test Cycle or Test Suite pages
  • When organizing imported Requirements from Jira by "Parent" field, the folder is named as "ID +Summary of the parent issue."
  • Ability to type ahead and search for agents by names when scheduling Test Run execution
  • Reduce the loading time of Test Run data query when there are a huge number of Test Runs included in the query result
  • parentId (ID of the module) of the Requirements are added to the response of following API calls:
    • GET /api/v3/projects/{projectId}/requirements
    • GET /api/v3/projects/{projectId}/requirements/{requirementId}

Bug Fixes

  • 12633 - Incorrect data in Test Run Details report
  • Values in Test Case properties of a Test Run do not match with the values from the associated Test Case version
  • 13186 - Unable to link a Jira story to a Test Run
  • 14168 - Unable to switch between pages when quickly clicking on objects such as Requirements, Test Cases and Test Runs on the tree
  • 14171 - It shows incorrect linked Requirements of a Test Case
  • 14174 - Unable to download attachments from TestPad
  • 14325 - When copying and pasting a Test Cycle to create a new copy of the same, custom field values of the Test Suites under the Test Cycle are not getting pasted
  • 14302 - Test Runs are added with the wrong order
  • 13356 - 2 scrollbars in Data Query pages
    • The scrollbar which were applied to the whole page is removed
    • You can collapse the Query section to have more space to view the query result grid
  • 11404 - Unable to use hot-keys to copy text from read-only fields
  • 13715 - API search artifact - Page size parameter is not working
  • 13787 - Self links to Test Runs are missing in the response of Get multiple Test Runs API
  • 13811 - Unable to insert line break in Notes section of Execution Log when submitting Test Logs using API POST /api/v3/projects/ProjectID/auto-test-logs?type=automation
  • 13912 - Unable to retrieve the test run via the SDK
  • 10933 - Blank entry in Test Run history
  • 12464 - Unable to run reports
  • 12940 - Unable to add assignee to projects using IE
  • 13155 - Unable to scroll down in Defect Data Query

Known Limitations

  • Displaying markdown formatted Jira fields (defect fields and requirements fields)
    • Impacts UI (Jira requirement, defect summary grid, and defects tab of TR) and Export Reports
  • When retrieving existing Fix Versions or Sprints to Manager for the first time, the progress bar seems to load forever, but actually, the objects have already been created in Manager. Please reload your Manager projects and check if they have been created successfully
  • For Jira Server: In case you only update a sprint goal and then you do not update any other sprint fields, the sprint goal will not be auto synchronized to Manager. You will need to manually click on the Retrieve button (in the JIRA configuration page or in an individual Release page) to get it updated.
  • For Jira Cloud: In case you only update a sprint goal without updating any other sprint properties, the sprint goal will not be auto synchronized to Manager. You will need to manually click on the Retrieve button (in the JIRA configuration page or in an individual Release page) to get it updated.
  • Reactivating a completed sprint is not auto updated to Manager since the Jira Webhook does not support this event.
  • For synced Fixed Version in Manager, there is a link for you to navigate to the corresponding Fix Version page in JIRA. However, there is no such link for synced Sprints for these reasons:
    • There is no URL for a specific sprint in Jira.
    • A sprint may be included on multiple boards in JIRA.
  • Test Case fields' values in Test Run grid do not match with those in the Excel export:
    • On Test Run grid: Test Case fields show values of the current associated Test Case version
    • In Excel port: Test Case fields always show values of the latest Test Case version
Powered by Zendesk