Managing Projects, Releases and Cycles


The Project module rights are assigned from Roles. It also includes rights for Release and Cycle considering the administrator is controlling Projects assigned to them along with the Releases and Cycles within that Projects.

Adding a New Project

Go to Projects > Project/Release/Cycle.

To add a new project in QMetry, click the New button on the toolbar.

It opens next screen with fields on it to add a new project.

 

  • Project Name: Enter name of the Project that is being added. A Project can be the current Project being tested and can contain multiple Releases and Cycles.

  • Project Key: The Project Key is a short-hand reference of the Project Name that will be used as a reference within the Project's test assets. Enter a Project Key with maximum limit of 5 characters. Name can include Alphabets, Number and supported special characters.

  • Description: Enter description regarding the Project.

Enable rich text editor

You can enable the flag to make rich text editor available in modules across the application. The rich text editor is applied to Large Text fields of modules. The settings are applicable at Project level.

Add new LDAP/SAML users to this Project

Enable the flag to automatically allocate the Project to new users added through LDAP/SAML.

Auto Create Values

The option is used to enable/disable the auto add of values to Lists - system lists as well as custom lists - while importing test assets through Excel. Enable the flag to allow creation of additional values (other than defined values) of Lists in QMetry.

Keep the flag disabled to avoid creation of additional list values in QMetry. This prevents from creating unwanted or junk values in the product and helps to keep the defined lists clean.

Use Case: Priority defined by Admin has three values Critical, Major and Low. This is as per customer business rule and Admin does not want users to add any other values than the defined ones. Users import an excel with priority as High, Medium, Trivial or any junk values like P1, P2, P3, etc. To stop users adding unnecessary values to Lists, Admin want to set the Auto Create Values flag Off.


If the values in QMetry are archived, the import will be blocked.

Once you are done with filling details and configuring settings, click Create to save the details and create a Project.

The project is added to the project list on the main screen.

Applying Filter to Project List:

Click on the Filter icon to make the Filter options visible.

Filter the project records either by Project name you have given to the project or by the Project Key.

Derivation of Test Case Execution Status from Test Case Step Status

The derivation of Execution Status of test case and test step depends on the Derive Test Case Execution status from Test Case step status settings done in the Project module. The settings remain “On” by default, which derives test case execution status from test case step status and vice versa. But there can be scenarios wherein the derivation of execution status is not required. For example, if any of the test steps is getting failed or skipped due to some reason but the user still wants to mark the test case as “Passed”.

To address the need, an option to disable auto-deriving test case execution status from step statuses and vice-versa is provided under Project Settings.

→ Required Permissions: Project “Modify” rights are required to set this flag at the project level.

  • When the Derive Test Case Execution Status from Test Case Step Status settings are turned “On”: By default, the flag remains On. The test case execution status derives from test case step status and vice-a-versa as per the set priority of Execution Status as described in https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/170098825 .

  • When the Derive Test Case Execution Status from Test Case Step Status settings are turned “Off”: When the flag is turned Off, users need to change the test case status manually as it will not get changed as per the status assigned to test steps underneath.

For more details, refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917#TestExecutionsScreen-ExecutingIndividualTestCases

Configure Resolved Status for Reports

Once the project is created, you can see the Default Resolved Status field on the project detail page.

Default Resolved Status: You can define which statuses to be considered for issues as "Resolved". By default the field shows "Resolved"  status. The reports also generated accordingly.

At least one status should have been selected as Default Resolved Status in this configuration.

The following reports will be generated in accordance with the configuration:

  • Resolved Issue Verification (under Issue Analysis Report)

  • Issue Created vs. Resolved (under Issue Trends Report)

The Default Resolved Status drop-down displays Issue Status values containing - QMetry System default values as well as Custom values for the Issue Status field and Jira list values imported along with Jira issues in QMetry.

  • Archived Issue Status: Archived Statuses are shown disabled on the Default Resolved Status drop-down. You can still select the status to show Issues having archived status on the report.

  • Issues linked across Projects: The records are displayed as per Resolved Status configuration.

When Jira is not Configured with QMetry

The Default Resolved Status will show QMetry Issue status in the drop-down. Select the status(es) you want to consider issues as resolved.

Adding a Release/Cycle

Open Projects module.

Open project details page by clicking on the Project Name on the grid.

The following tabs are there on the screen:

  • Release/Cycle

  • Users

  • Jira Integration (as per permissions set in Administration > Roles)

  • eSignature

  • BDD Configuration

Adding Releases under a Project

One Default Release is provided when you create a Project.

  1. On the project details page, click on the '+' icon and select Add Release on it.

  2. A blank row appears on the screen to enter release details.

  3. Enter the Release Name, Release Start Date, Release Completion Date in sequence and click Add.

  4. The Release is added on the list.

Adding Cycles under a Release

Cycles are added within respective releases. Once Default Cycle is provided under the Default Release.

  1. Click on the '+' icon and select Add Cycle on it. A blank row appears on the screen to enter Cycle details.

  2. Select Release within which the Cycle is to be added.

  3. Enter the Cycle Name, Cycle Start Date, Cycle Completion Date in sequence and click Add. Cycle Start and Completion Dates should be within Release Start and End Date. Now click Add.

  4. The Cycle is added under the selected Release.

Expand Release to view Cycles added under it.

Default Release, Default Cycle: On creation of project, one default release and one default cycle are added within that project; making the scope as Project – Release – Cycle.

You can edit the names of default release and cycle.

You cannot archive and delete the system default release/cycle.

Users whose assigned user role has project rights assigned can access the project.

Editing a Release/Cycle

  1. Hover the mouse over the field values and the Edit icon becomes visible.

  2. Click on the Edit icon and change the required value.

  3. Save individual values after editing.

Deleting a Release/Cycle

1. To delete a Release/Cycle, first you need to archive that release/cycle. To archive release and archive cycle, click on the Archive button under the Action column on the respective grid.

2. The Release/Cycle is archived after confirmation. Once the Release/Cycle is archived, you can not edit it.

Note: If a Release is archived, then all the Cycles under the Release are also archived.

3. The Action column now shows Unarchive and Delete buttons for archived Release/Cycle.

4. To delete the Release/Cycle, click on the Delete button. The Release/Cycle should be archived first to delete it.

To unarchive the Release/Cycle, click on the Unarchive button.

Making Build Selection Mandatory

Note: Mandatory Build features will be visible only if you have purchased Customization package.

You can make the build selection mandatory for a given project. Make build mandatory works in accordance with Project Create and Modify rights. You can set the Make Build Selection Mandatory settings while creating a new project or while editing an existing project.

Use Case : The organization has hundreds of builds in multiple projects. If a tester does not mention the build number, it becomes difficult to track on which build the test was executed against after a few days. In such cases, QA Manager has the option to make the build selection mandatory while executing a test case.

Make Build selection mandatory during execution: This option is available on the Project create and edit screen (Projects > Project/Release/Cycle.). This will enforce Build selection on the Test Suite Execution Screen. Select the check box to make Build selection mandatory when test cases are being executed on the Execution Screen. The test execution will not be carried out without build selection.

Audit logs are also maintained for the changes made to the “Make Build selection mandatory during execution” settings.

Note: Bulk Execution performed on the “Bulk Execute” screen (Test Suite > Test Execution tab > Bulk Execute) is exempted from mandatory build selection. All the bulk executions from this screen will be performed on None build.

Steps to make a build selection mandatory while creating a new project:

  1. Go to Projects > Project/Release/Cycle.

  2. Click on the New button to create a new project.

  3. Select the Make Build selection mandatory during execution check box to make the build selection mandatory before proceeding towards execution.

Steps to make a build selection mandatory while editing an existing project:

  1. Go to Projects > Project/Release/Cycle. You can see the list of created projects.

  2. Open the project by clicking on the project name. The edit screen opens.

  3. Select the Make Build selection mandatory during execution check box to make the build selection mandatory before proceeding towards execution.

If you have enabled the Make Build selection mandatory during execution option in Projects module, you can see the tip “Build is set as Mandatory during execution” on the Build grid (Projects > Builds).

Tester will see the following message when Build Selection is mandatory in the project and no build is selected on execution screen.

Editing a Project

Users can edit values of Project Name and Description, and change other settings .

  1. Go to Projects > Project/Releae/Cycle. It displays the list of Projects of which you have rights.

  2. Open project detail page by clicking on the Project name on the list.

  3. Hover the mouse over Project Name and Description to change respective values by clicking on the Edit icon.

  4. Configure settings for Enable Rich Text, Add in LDAP/SAML by Default  and Auto Create Values.

Archiving Projects

You can archive Projects which are no more required. Users with "Modify" Project rights can archive projects. The rights also allow the users to archive Release and Cycle.

Use Case: Work on a Project is finished and the Admin does not want the team to see the Project and its associated Releases and Cycles. So the Admin decides to archive the Project.

  1. Go to Projects > Project/Release/Cycle.

  2. It displays the list of Projects of which you have rights.

  3. Click on the Archive button for the Project that you want to archive.

You can also archive project from project detail page. Open the project detail page and click on the Archive icon at the top right corner of the screen.

Notes:

  • Archived Releases and Cycles will be hidden on the respective lists across all modules.

  • Once a project is archived, the project name will not appear on the Project list.

  • Archived projects can not be edited.

Unarchiving Projects

  1. Once a project is archived, there are two buttons enabled for it – Unarchive and Delete.

  2. Click on the Unarchive button to unarchive the archived project.

Cloning a Project

Note: User should have “Clone” rights for Project to be able to clone the project.

Users can add a clone of an existing Project with either Folder Structure or Folder Structure along with Data.

 

  1. Go to Projects > Project/Release/Cycle. It displays the list of Projects of which you have rights.

  2. Click on the Clone button for the project you want to clone.

  3. The next screen opens with Project Name and Project Key fields on it. Make required changes to the Project Name and Key. By default, it will suffix  "_copy" to the Project Name.

Select either of the options:

  • Folder Structure: It will copy the folder structure along with releases and cycles. It will not copy assets contained in the folders.

  • Folder Structure along with Data: It will clone project meta-data and requirements, test cases, test suites within folders along with releases cycles.

Then click on the Clone button.

View the Progress of Clone

When you complete the cloning process, the message pops up to view notification for the clone progress. You can view the progress in the notification window on the application header. This allows scheduled clone operations to run in the background and allows users to continue with their other work.
Check the notification window on the application header. It shows the list of Activities.

Scheduled Task

Click on the Scheduled Task  icon the application header. The Scheduled Task icon turns Orange in color whenever any of the following actions is initialized. The icon color changes to original as soon as you click on it to view the task status.

  • All bulk operations

  • Import - IS, TC, TS, RQ

  • Export - IS, TC, TS, RQ, Test execution

  • Project clone

The screen shows all the activities completed or in queue.

For the Clone activity that has been carried out, you can view the details of Activity Executed By, Source Project, and Destination Project.

Deleting Projects

First, archive the Project as described in Archiving Projects.

To view archived projects on the Projects screen, select the Show Archived check box on the Project list view.

Once the Project is archived, then only you can see the Delete button on the screen. Users can delete a project only if it is archived.

Click on the Delete button to delete the project.

 

Unarchive a Project

To view archived projects on the Projects screen, select the Show Archived check box on the Project list view.

Once the Project is archived, then only you can see the Unarchive button on the screen.

Assign a Project to Users

After users have been added (as described in the article Users)you can link users to a project and control their permissions. You should be a Project Administrator to use this functionality.  Each project has its separate data, users and settings. When a user is linked to a project, they can access the project in accordance with the role assigned to them. 

 

  1. Open the Project detail page by clicking on the Project name. It opens the screen with tabs on it.

  2. Open the Users tab. It lists out all the users associated with the Project, in other words, the users who are allowed to use the Project. The columns display Name, Username, Role, and Status details of the user.

  3. To open the list of available users, click on the Link button above the grid.

  4. Select users and their Role for the project.

  5. To link a single user, click on the Link icon for the user.

  6. To link multiple users, select users and then click on the Link Selected Users button at the bottom.

To add a new user click on the Create New User link available beside the Link button above the grid.

To remove the User Role mapping with project for a user, click on the Unlink button for that user.

To unlink multiple users at a time, select users on the grid and click on the Unlink Selected button.