Back to QMetry All Products Help Page
Managing Projects, Releases and Cycles
Introduction
QMetry offers a range of user-friendly features for managing projects, releases, and cycles enabling seamless coordination, efficient tracking, and timely alignment of test activities with development milestones, ensuring high-quality software delivery.
Notes:
Project module rights are assigned through Roles, including permissions for Releases and Cycles, allowing administrators to manage Projects, Releases, and Cycles assigned to them.
To make the most of these features, it’s important to know how to set up and configure the projects.
Managing Projects
QMetry enables users to manage projects efficiently by providing a comprehensive suite of tools for creating new projects, managing user access, tracking progress, collaborating with team members, and ensuring that all project requirements are met effectively.
To make the most of these features, it’s important to know how to set up and configure the projects.
Creating New Project
User can add a new project from:
- Projects > Project/Release/Cycle
To add a new project in QMetry, follow these steps:
Click the "New" button on the toolbar.
Enter the project name.
Enter the project key.
Provide a description summarizing the project.
Configure the project settings as required.
Click "Create."
Notes for creating Project Name and Project Key:
These special characters are not supported in the project name:
\ / : * ? < > |
A project name can include alphabets, numbers, and supported special characters in it.
Project key is a short-hand reference of the Project Name that will be used as a reference within the Project's test assets.
A project key can be of 10 characters.
The project key can’t be edited once it is created.
A project key can include alphabets and numbers in it.
Only new projects can be added with the key maximum up to 10 characters.
Project configuration available on the Create Project page -
Rich text editor
QMetry’s project description field supports rich text formatting, enabling users to include bold, italics, lists, hyperlinks, images, tables, and code snippets for enhanced clarity and presentation.
→ To use this feature, toggle the "Rich Text Editor" switch.
Add new LDAP/SAML users
QMetry supports LDAP and SAML user logins, allowing seamless integration with existing directory services and single sign-on (SSO) for streamlined user authentication and management.
→ To use this feature, toggle the "Add new LDAP/SAML users to this Project" switch.
Derive Test Case Execution status from Test Case step status
Deriving test case execution status based on the individual test case steps statuses ensures that the final status accurately reflects the results of its constituent steps.
→ To use this feature, toggle the "Derive Test Case Execution status from Test Case step status" switch. By default, this setting is enabled.
When Enabled:
The test case execution status is automatically derived from the status of the test case steps.
When Disabled:
Users can manually set the test case execution status.
Enable eSignature
The e-signature functionality ensures that approvals and validations are formally recorded and can be securely tracked, enhancing compliance and accountability in the testing process.
→ To use this feature, toggle the "Enable eSignature" switch.
Make Build selection mandatory during execution
Note: Mandatory Build features will be visible only if you have purchased Customization package.
Making Build selection mandatory during execution ensures that every test run is associated with a specific build version, thereby enhancing traceability and accuracy in testing results.
→ To use this feature, toggle the "Enable eSignature" switch.
If Make Build selection mandatory during execution is enabled in Projects module, the tip “Build is set as Mandatory during execution” on the Build grid (Projects > Builds) is displayed.
If build selection during execution is set to mandatory, users will get the following message if no build is selected on execution screen.
Define Dependency Between Test Cases
Test Case Dependency feature enables the user to set successor and predecessor dependency among test cases, wherein the execution of the successors depends on the successful execution of the predecessors.
→ To use this feature, toggle the "Define Dependency Between Test Cases" switch.
Risk Analysis
Risk Analysis feature helps testing teams prioritize efforts by identifying and managing risks associated with requirements and test cases.
→ To use this feature, toggle the "Enable Risk Analysis in the Project for the below entities" switch.
Refer to Risk Based Testing: Auto Calculation of RPN and Extent Of Testing for more details on Risk Analysis feature of QMetry.
After creating a project, users can configure the project settings by clicking on the project key. The project details page will display the following tabs:
General Settings
Release/Cycle
Users
Integration (as per permissions set in Administration > Roles)
BDD Configuration
Automation Tool
General Settings
Once a project is created, users can customize its settings further. To do this navigate to:
- Projects > Project/Release/Cycle
Click on the specific project to access the project’s general settings.
Users can reset previously defined configuration values—such as rich text editor, test case dependencies, mandatory build selection, test case execution status, and risk analysis —through the project's General Settings (These features are elaborated in the above section).
In addition, users can also configure the following features:
Auto Create Values
Auto-creation of list values during Excel imports ensures users can only import values that are not already defined in QMetry’s system or custom lists.
Use Case: Suppose the admin has defined three priority levels as Critical, Major, and Low, according to business rules and wants to prevent users from adding other values. By disabling the Auto Create Values flag during Excel imports, users are restricted from adding junk notations like P1, P2, P3.
Default Resolved Status
Once a project is created, users can see the “Default Resolved Status” field in the project general settings page.
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. Users can 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.
By default, "Resolved" is set as the Default Resolved Status. Users can change this to Closed, Open, or Reopened, but the field cannot be left blank.
This configuration affects the following reports:
Resolved Issue Verification (under Issue Analysis Report)
Issue Created vs. Resolved (under Issue Trends Report)
Latest Test Case Execution Status
The latest test execution status offers quick insight into a test case's performance, helping track progress, spot issues, and make decisions regarding software quality and stability. This status is accessible in the list view of the Test Case module.
Users can configure test case execution status for both the - project scope and test case version.
Test Execution Project Scope
Select whether to calculate the latest test execution status based on test executions from the current project or all projects:
Current Project: Only test executions from the current project are considered
All Projects: Test executions from all projects are considered.
Test Case Version
Select whether to calculate the latest test execution status based on the latest version or all versions of a test case:
Latest Version: Only executions of the latest version are considered.
All Versions: Executions of all versions are considered.
For more details on test execution statuses, refer to Test Execution Screen Default View | TestExecutionScreenDefaultView ExecutingIndividualTestCases
Refer to the Execution Status Management Document to learn how to customize the latest execution statuses of test cases.
Release/Cycle
Users can add a Release/Cycle to a project for organizing and managing test activities. Navigate to the release/cycle tab in the project details page.
Adding Release
During project creation, a default release is assigned. Users can add a new release to the project by following these steps:
Navigate to the Release/Cycle tab and click the '+' icon.
Select "Add Release."
Enter the release name, release start date, and release completion date in the respective fields, then click "Add."
The new release will be added to the list.
Adding Cycles under a Release
Cycles are added within respective releases. During project creation, a default cycle is assigned. Users can add a new release to the project by following these steps:
Click the '+' icon and select "Add Cycle."
A blank row will appear for entering cycle details.
Select the Release within which the cycle will be added.
Enter the Cycle Name, Cycle Start Date, and Cycle Completion Date in the respective fields, ensuring that the cycle dates fall within the Release Start and End Dates.
Click "Add."
The cycle will be added under the selected release.
Expand Release to view Cycles added under it.
Editing Release/Cycle
Users can update the release and cycle of a project. These are the steps to edit release/cycle.
Hover the mouse over the field values and the Edit icon becomes visible.
Click on the Edit icon and change the required value.
Save individual values after editing.
Deleting a Release/Cycle
Follow these steps to delete a release/cycle:
Archive the Release/Cycle: To begin, click the "Archive" button in the Action column of the respective grid to archive the release or cycle.
Confirmation and Archival: After confirmation, the release or cycle will be archived. Note that archived releases or cycles cannot be edited.
Action Options: Once archived, the Action column will display "Unarchive" and "Delete" buttons for the archived release or cycle.
Delete the Release/Cycle: To delete, click the "Delete" button. Remember, a release or cycle must be archived before it can be deleted.
Editing a Project
Users can modify the project name, description, and reset project settings on the Edit Project page.
To edit a project, follow these steps:
Navigate to Projects > Project/Release/Cycle.
A list of projects for which the user has access rights will be displayed.
Open the project detail page by clicking on the project name from the list.
Hover over the Project Name and Description fields to reveal the Edit icon.
Click the Edit icon to update the respective values.
Configure settings for the available options as needed.
Archiving Projects
Users can archive projects that are no longer needed. Here are the steps to archive a project
Go to Projects > Project/Release/Cycle.
This will display a list of projects to which the user has access rights.
Click the "Archive" button next to the project. The project will be archived upon confirmation.
Users 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.
Cloning a Project
The Clone feature in QMetry lets users create a new project similar to an existing one, avoiding the need for the extensive setup to configure a project from scratch. After creation, the new project can be independently modified. Users can choose to clone either just the folder structure or both the folder structure and associated data.
Steps:
1. Go to Projects > Project/Release/Cycle.
It displays the list of Projects for which the user has rights.
2. Click on the Clone button for the project to clone.
On the project clone screen, the Project Name and Project Key fields are set by default by adding the suffix ‘_copy’. Users can modify these fields as needed.
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.
A confirmation pop-up will appear stating that the source project will be in read-only mode during the cloning process. Click 'Yes' to proceed immediately or 'No' to postpone the action for later.
View Cloning Progress
Upon initiating the cloning process, a message will prompt users to view the notification for clone progress. Users can monitor the progress in the notification window on the application header.
For the completed Clone activity, users can view details such as Activity Executed By, Source Project, and Destination Project.
Scheduled Task
Click on the Scheduled Task icon the application header. The screen shows all the activities completed or in queue.
The Scheduled Task icon turns Orange in color whenever any of the following actions is initialized:
All bulk operations
Import - IS, TC, TS, RQ
Export - IS, TC, TS, RQ, Test execution
Project clone
The icon color changes to original as soon as you click on it to view the task status.
Deleting Projects
Users can delete a project only if it is archived. Here are the steps for deleting a project:
1. First, archive the Project as described in Archiving Projects.
2. 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 users can see the Delete button on the screen.
3. Click on the Delete button to delete the project.
Unarchive a Project
To unarchive a project, follow these steps:
On the Projects screen, check the "Show Archived" box to view archived projects.
For archived projects, two buttons will be available: Unarchive and Delete.
Click the "Unarchive" button to restore the archived project.
Assign Project to Users
After adding users, project admins can link them to a project and manage permissions. A user linked to a project can access it according to the role assigned to them.
To manage users for a project, follow these steps:
Access the Project detail page by clicking on the project name.
Navigate to the Users tab to view all user details associated with the project, including their Name, Username, Role, and Status.
To view the list of available users, click the Link button above the grid.
Select the users and assign their roles for the project.
To link a single user, click the Link icon next to the user’s name.
To link multiple users, select the desired users and click the Link Selected Users button at the bottom.
The following operations can be performed on this screen:
Add a New User: Click the Create New User link located beside the Link button above the grid.
Remove User Role Mapping: Click the Unlink button next to the user.
Unlink Multiple Users: Select the desired users in the grid and click the Unlink Selected button.
Back to QMetry All Products Help Page