Menu

Manager 8.9.0 Release Notes

8.9.0 Release Notes-January 2, 2018

Plugin Updates

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

End of Support Announcement

  • Beginning with Manager 8.9, qTest APIs will no longer be accessible using HTTP. Please make sure to change your target URLs to use HTTPS instead or accept a 301 response as a successful response

New Feature

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

Release_integration.png

  • 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.
  • When adding Requirements to a Jira Release, only Requirements created internally in Manager are included in the tree. Requirements from Jira are excluded.
  • 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.

Release_scope.png

Enhancements

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.

Test_Plan_tab.png

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

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

Known Issues - Limitations

  • 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.
  • When adding Requirements to Jira Release scope, although Jira Requirements are excluded from the Requirement tree, you are still able to search and add them to the Release scope. It is highly recommended that you do not do so. Instead, please update the Fix Version or Sprint scope in Jira.
  • 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