Menu

Import and Use Releases from JIRA

Overview

qTest Manager allows you to manage standalone releases and releases from JIRA. Importing releases from JIRA allows testers to use up-to-date information from JIRA sprints & fix versions.

Note: Instructions to import and use releases from JIRA are the same, whether you are using JIRA Server or JIRA Cloud.

Before importing releases from Jira, please make sure to complete the setup steps described in the following sections:

Configure Release Integration

  1. On the Configure Connection page, select the Toggle icon in the "Release Integration" area of the screen to activate the release integration feature.

    Release_Integration_-_Deactivated.png

    The toggle button is switched ON.

    Release_Integration_-_Activated.png

  2. Select Add Release Type. The "Add Release Types" dialog displays

    Add_Release.png

  3. Select the down arrow to the right of the JIRA project field. From the drop-down list, select the applicable JIRA project from which you will import requirements to qTest Manager
  4. Select the down arrow to the right of the JIRA Artifact types field. Select the artifact type you use to represent releases in the JIRA project selected above (e.g., sprint, fix version). This procedure will retrieve that object type so that it imports into qTest Manager as releases.

    HINT: The purpose of this step is to identify the artifact type from the JIRA project and import that object type into qTest Manager as releases.

  5. Select OK. A line is created in the Release Integration area of the Configure Connection page for the JIRA project and associated JIRA artifact type selected in the steps 3-4 above.

    Release_type_grid.png

  6. Position the arrow cursor on the new line that indicates the JIRA PROJECT and JIRA ARTIFACT TYPES. Then, move the arrow cursor into the ACTIONS column on the right side of the window. Three icons display under that column. Select the wrench icon.

    Release_type_grid_-_wrench.png

  7. On the Edit Data Retrieval screen, you can configure two things:
    1. Status of selected artifact type (sprint or fix version) that you wish to retrieve to your Manager
    2. Auto-populate requirements in Release Scope

    HINT:

    • This step configures the status of artifact types that populate within qTest Manager as releases and then links imported Jira requirements to imported releases as the latest release scope from Jira.
      Note: only JIRA Requirements will be added to corresponding JIRA Releases
    • The scope of Fix Versions and Sprints in JIRA is real-time updated in Manager (if this function is enabled)
    • You are not able to add JIRA requirements to a JIRA release scope or remove JIRA requirements out of a JIRA release scope.
    • If you manually add a standalone Requirement of Manager to a JIRA Release scope, the link will remain after any data update from JIRA

    For Fix Version

    Fix_Version_-_Data_Retrival_config.png

    For Sprint

    Sprint_-_Data_Retrival_config.png 

  8. Select OK. Then, select Save & Activate.

    Save_and_Activate.png 

    The "Confirmation" dialog displays.

    confirmation.png

Retrieve Jira Data

After you finish all the above steps to configure your Release Integration for JIRA Connection, you can configure your JIRA Artifacts to populate within Manager. There are two ways to go about doing this:

  1. Position the arrow cursor on the new line that indicates the JIRA PROJECT and JIRA ARTIFACT TYPES. Then, move the arrow cursor into the ACTIONS column on the right side of the window. Three icons are displayed under that column. Select the retrieve icon.

    Retrieve.png 

  2. Select Retrieve Jira Data.

    Retrieve_all.png 

    The "EXTERNAL RELEASE RETRIEVING PROGRESS" dialog displays. A progress bar displays.

    Progress_bar.png 

    When qTest Manager has imported all configured JIRA artifacts, the following message is displayed:

    Progress_bar_-_Completed.png 

  3. Select OK. The releases created in JIRA will be accessible to testers in qTest Manager. Its properties will separate into two sections: one for Manager’s Properties and a Read-only section for JIRA’s Properties.

Review Jira Releases After ImportReleases_imported_from_JIRA.png

  1. Select the Test Plan module from the header and view the releases imported from JIRA. These are located in the navigation panel. Each of these objects represents an object in JIRA. Imported Jira's artifacts are represented by with the Atlassian symbol JIRA_release_icon.png to differ from internal qTest releases qTest_release_icon.png.

Imported JIRA artifacts update in real-time, but you may have to reload the release page if you are on the actual page when a change is made on the issue in JIRA. An imported JIRA artifact has two Properties sections - JIRA's Properties and qTest's Properties.

JIRA Properties contain:

  • For Fix Version: Link, Start Date, End Date & Description
  • For Sprint: Start Date, End Date & Sprint Goal

These Properties are Read-only and can be updated in real-time. In case you only update a sprint goal without updating any other sprint properties, the sprint goal will not be automatically synced to Manager. You will need to manually select Retrieve (in the JIRA configuration page or in an individual Release page) to update it. Currently, JIRA Properties' fields cannot be used for searching in qTest Manager.

HINT: Start Date & End Date on qTest’s Properties are Read-only & their values are from JIRA Properties.

  1. To view the actual JIRA artifact – Fix Version for a particular release, click the Link hyperlink to be redirected into JIRA. For Sprint, it just shows name of Sprint without hyperlink

For recommendations on incorporating the Release Integration into your qTest + Jira workflow, check out this article: Best Practices on Jira Release Integration.

Powered by Zendesk