Create/View Test Cycles


Test Cycle allows the testers to perform Test Execution in a tracked and organized manner. QMetry provides the users with a quick and efficient process of creating a Test Cycle. Additionally, you can carry out all the functionalities related to the Test Cycle from the 'Create Test Cycle' detail page.


Users should have the “Test Cycle Create” permission for the project to be able to create a test cycle in the QMetry Jira add-on.

Steps to Create a Test Cycle

You can create a new test cycle and directly associate it with a folder.

1. Select a folder on the tree at the left.

2. Click on the New button at the right. The new test cycle will be created in the folder you selected on the tree.

There are five tabs on the 'Create Test Cycle' screen: Detail, Test Case, and Attachments. Once the test cycle is created, Comments and Audit Logs tabs will be visible.


3. Enter Test Cycle Details.

  • Summary: It is a short summary of the test cycle.

  • Description: It describes the test case with more details like images, links, etc. The field has Wiki markup editor. You can use different options that are available to apply on the text. Refer to Text Formatting.

Permissions and configurations required for tagging users and receiving email when tagged.

1. Required Jira Permissions for tagging users:

a. Jira Settings > Global Permissions > Browse users and group: The user and “atlassian-addons-admin” groups should be part of this permission to be able to tag users.

b. Project Settings > Permissions

i. Assignable user: The users having this permission can be tagged.

ii. Assign Issues: The users having this permission can tag other users.

2. Required configurations to receive email notifications from QMetry:

Set the email visibility to ‘Anyone’ for receiving email notifications on getting tagged. For this configuration, go to Profile and Settings > Account Settings > Profile and Visibility > Contact > Set the email visibility to ‘Anyone’. The user’s email address will be visible to QMetry once the configuration is set to ‘Anyone’.

  • System Fields: These are system defined fields. Enter/select values for the fields. The list values are entered in Configuration > Project Configuration.

    • Folder Path: It shows the folder path of the test cycle where it is located.

    • Priority: It shows how important the test cycle is with priority assigned as - blocker, critical, high, low, etc. You can configure the priority list values from Configuration > Priority.

    • Status: It shows the workflow of the test cycle with Statuses like To Do, In Progress, Done, etc. You can configure the status list values from Configuration > Statuses.

    • Assignee: It shows the user who is assigned to work on the test cycle. The user's list display users who have access to the project.

    • Reporter: It shows the user who has created the test cycle. The user's list displays users who have access to the project.

    • Components: It references Project Components that you have created in Configuration > Components like UI, Configuration, etc.

    • Labels: It is helpful to group test cycles into categories. You can configure the Labels list values from Configuration >Labels.

    • Sprint: The field is useful for Agile methodology where planned tasks have to be completed by the team and made ready for review. It shows the Sprint in which the test cycle is included.

    • Fix Versions: It shows the version of the software in which the issue is fixed. The field values come from Jira.

    • Planned Start Date, Planned End Date: Users can mention the approximate time of the Cycle - on which date it will start and end.

  • Custom Fields: Users can add additional fields other than system fields. Custom Fields are added from Configuration > Custom Fields.

4 . Once you are done entering details, click Create to create the test cycle.


Create another:

The Create another check box allows users to keep creating one test cycle after another without having to click on the Create button again and again. It is helpful when you have to create a series of test cycles.

While creating another entity, values of some fields populate as these field values get preserved.

Field values that will be preserved

Field values that will not be preserved

Field values that will be preserved

Field values that will not be preserved

  • Folder Path

  • Priority

  • Status

  • Assignee

  • Reporter

  • Components

  • Labels

  • Sprint

  • Fix versions


  • All Custom Fields

  • Summary

  • Description

  • TestCase

  • Attachments

Users can link multiple existing test cases with the test cycles. Read more details on


Test Cycle List View

You can view the Execution Summary of test cycles from the test cycle list view. The Execution Summary (Tabular) column is added to the Test Cycle list view to show the exact count of test case execution status. Enable the column Execution Summary (Tabular) from the Column drop-down.

Note: A maximum of 40 columns can be selected at a time to display.

The execution result columns are added with the count of test case execution status.