View Traceability in Jira Server

View Traceability for Story, Test cases, Executions, and Bugs.

Prerequisites

  • Integrate your Jira Project with a QMetry project.

  • Enable QMetry Configuration in the Jira Project.

  • Complete mapping of Jira and QMetry Work Items.

  • Authenticate your Jira connection:

    • Login to QMetry and select Integrations.

    • Select Jira Integrations.

    • On the Integrations tab, click the cog icon.

    • Select Configure and enter the Jira Credentials.

Jira Story synced as QMetry Requirements having linked Test Cases

QMetry Panel in Jira

The QMetry panel in Jira shows the Test Case and test steps details along with Test Execution.

  1. Go to the Jira Story that is synced with QMetry Requirements linked to Test Cases.

  2. Select the QMetry Project from the projects dropdown list with which the Jira story is synced. If the story is synced in more than one QMetry project, the list shows all linked projects. When you select a project, the Entity Key populates for the story synced in QMetry as a requirement.

    Note

    When you open a synced Jira issue type from within a QMetry project, the QMetry Project list automatically selects the originating QMetry project.

  3. Under Story, the Test Cases section displays all the Test cases linked to the Requirement. The test case and steps details are shown with respect to the version linked with the Requirement.

    Note

    The latest execution status shown in the test case details is irrespective of the version linked to the Requirement - it’s the latest (based on the timestamp) executed status of the test case.

  4. Expand the test case row to view Test Case Steps and Executions details of the test case.

  • Total Executions:

Total executions

Clicking on the count will open the Executions tab of the Test Case View in the Jira Add-on, which shows all the execution details. Refer to Test Case View in Jira Add-on below on this page.

Test Case Steps

The Test Case Steps tab displays the test case steps of the test case version linked with Requirement. Clicking the Test Case Key opens the Test Case Details screen in Jira.

QPro_JI_TestCaseSteps.png

Executions

The Executions tab displays Test Case Executions for a combination of test suite, release, cycle, platform, and executed version, for all versions that test case.

Jira New View

Clicking the Test Suite Key opens the Test Suite page in QMetry.

If the issue is directly linked to the test case without its execution, then the Executions tab does not show any execution details.

No_Executions.png

If a bug is linked to the test case, the count is displayed in the Bug column. The bug details are available by clicking on the count, which opens up the Issues pop-up. Clicking on the Issue Key opens the issue detail page in Jira.

Total Executions

The Total Executions column displays the count of all executions performed for the test case.

QPro_JI_ViewTotalExecutions.png

The Total Executions column in the QMetry Test Case panel shows how many times a test case has been executed. Click the count to open the execution details in the Test Case View.

Product owners, QA managers, and testers who review test cases in Jira can see how often a test case was executed and then drill down into each execution.

If a Jira Bug or Story is linked with a test case in QMetry, the Executions tab in Jira displays the total issues linked to the execution. The count is clickable and it displays the issue details.

QPro_JI_ViewTotalExecutionsClickEvent.png

Test Run UDFs

Test Run UDFs are user-defined fields that testers fill in when executing a test case in QMetry. In Jira, you can view the values entered for each execution without leaving the issue.

Visibility Conditions

  • The Test Run UDFs column and tab appear only if Test Run UDFs are associated with the Test Run module of the selected QMetry project.

  • If the selected project has no Test Run UDFs, the column does not appear in the column selection list.

Test Run UDFs Icon

The icon in the Test Run UDFs column shows at a glance whether the execution data is complete.

Icons

Meaning

Green icon with a star

All mandatory Test Run UDFs have values.

Blue icon with a star

At least one mandatory Test Run UDF is blank.

Blue icon without a star

The execution has no mandatory Test Run UDFs.

To View Test Run UDFs from the Executions Tab
TestRunUDFinQMetryPanel.png
  1. In the QMetry panel, expand the test case row and open the Executions tab.

  2. Click the icon in the Test Run UDFs column for the execution. The Test Run UDFs dialog box opens and lists each UDF with its selected value.

Mandatory UDFs are marked with a red asterisk. Large Text UDFs display rich text formatting.

To view Test Run UDFs from the Test Case View
  1. Click the Test Case Key to open the Test Case View in Jira.

  2. On the Executions tab, expand the execution row.

  3. Open the Test Run UDFs tab.

Test Case View in Jira Add-on

A test case is created and linked with a test suite in QMetry. Release & Cycles and Platforms are associated with the test suite for test execution. On the execution screen, the Jira issue is linked with a test case as an external issue. The issue link opens in Jira.

  • Clicking on the Test Case Key in the Test Case section will open the Test Case View in Jira.

  • The test case detail page in Jira displays Execution & Test case details in separate tabs.

    • Execution tab displays

      • Test case executions for a combination of the test suite, release, cycle, platform, and executed version.

      • Test case step execution details.

      • Linked Bugs, Test logs, Comments for the test executions, and test step.

→ If the issue is directly linked to the test case without its execution, then the Executions tab will not show any execution details.

  • Test case details display complete test case information.

Test Case Details

The Test Case Details tab displays details of system fields as well as user-defined fields entered for the test case in QMetry and its Execution Status Summary.

Test case details

Executions

The Executions tab displays test suites in which the test case was executed. The test suite link opens in QMetry. You can view Bugs, Attachments, S.C. (Step Count), and Comments for the test case. The counts can be clicked to expand the test suite row to show its relevant tab in the expanded area. Other columns include Executed by and A.T. (Actual Attendant Time). The columns are resizable for better visibility.

Each test suite row is expandable. The expanded area has four tabs on it: Steps, Issues, Attachment, and Comments.

→ If the issue is directly linked to the test case without its execution, then the Executions tab will not show any execution details. The page will appear blank with a relevant message on it.

Executions

Prerequisites

Bugs linked from the Test Suite Execution Screen in QMetry

When a test case is marked as failed during the execution, and a bug is raised on the Test Suite Execution screen, that bug gets raised in Jira and its external key (Jira issue key) is shown in QMetry. On clicking on the External Key of the issue in QMetry, it opens bug details in Jira. The Test Cases section on the Jira issue details page also displays the Linkage Level of the issue - Test Case/Test Step along with other details of the test case.

Expand the test case row to view Test Case Steps and Executions details of the test case.

On expanding the test case, two tabs are displayed:

  • Test Case Steps: The Test Case Steps tab displays the test case step details.

    test case steps
  • Executions: The Executions tab displays details like Test Suite Key, Test Suite Summary, Executed Version, Platform, Release, Cycle, Status, linked Bug (click on the icon to view the details), Attachments (click on the icon to view the details), Comments and Executed by. Test Suite Key has a link on it, clicking on which opens the Test Suite page in QMetry.

    Executions tab

BDD Panel in Jira when Jira stories are synced in QMetry

When a version control system is configured for the QMetry project, the BDD panel will be visible in the stories imported as requirements. The BDD panel in QMetry will appear read-only for the requirement imported from Jira; however, any changes made in the BDD panel in Jira will reflect in the BDD panel in QMetry.

Scenario: If one Jira project is configured with more than one QMetry Project and Jira stories are synced in QMetry. Here, one Jira story is synced in more than one QMetry project.

QMetry Project: It displays QMetry Projects with which the Jira story is synced and the version control system is configured. In this case, the drop-down will show more than on QMetry Project.

  • For the selected project, provide BDD Configuration details to pull the BDD details.

  • Version Control list will populate according to QMetry Project selection.

  • The repository list will populate according to selected Version Control.

  • Whatever changes you make in BDD and push, it will impact only the selected QMetry Project.

    BDD

Traceability in QMetry

  1. Go to Reports > Open Traceability report.

  2. Select Trace by :

    1. For Requirement Traceability: Select Trace by Requirement

    2. For Issue Traceability: Select Trace by Issue

  3. Select entity > Apply

    Report
Publication date: