Managing Projects
Create, clone, archive, or delete projects. Configure general project settings, link releases and cycles, add users, and perform various other actions.
Note
Get project module rights from Roles under the Customization.
Managing Projects
Manage projects within QMetry with a comprehensive suite of tools for creating new projects, managing user access, tracking progress, collaborating with team members.
Creating New Project
Note
The create project operation auto-creates a default release and cycle in the new project, even if the user does not have the Create, Modify and Delete Rights for Release & Cycle.
To add a new project, follow these steps:
Go to Projects and click .
Enter the project name and key.
Provide a description summarizing the project.
Configure the project settings as required.
Click Create.
Note
Rules dor creating Project Name and Project Key
Special characters are not supported in the project name:
\ / : * ? < > |A project name can include alphabets, numbers, and supported special characters.
Project key is a short-hand reference of the Project Name 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, numbers, and supported special characters and numbers in it.
Only new projects can be added with the key maximum up to 10 characters.
 |
Rich Text Editor
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 or SAML users
LDAP and SAML user allows 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 e-Signature
The e-signature functionality ensures that approvals and validations are formally recorded and can be securely tracked.
To use this feature, toggle the Enable eSignature switch.
Make Build Selection Mandatory during Selection
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.
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.
Audit logs are maintained for the changes made to the Make Build selection mandatory during execution settings.
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.
Note
The Risk Based Testing feature is only available with the Advanced Features pack of QMetry.
After creating a project, configure the following project settings by clicking the project key:
General Settings
Release/Cycle
Users
Integration
BDD Configuration
Automation Tool
Refer Risk Based Testing documentation to know more.
Enable Auto-Sync All Executions on New Test Case Version
This setting allows Project Admins to control whether users can automatically sync all executions with the latest test case version when creating a new version.
This setting helps teams preserve execution history, avoid accidental resets of prior versions, and maintain compliance in regulated environments.
Note
This setting is not available for e-signature-enabled projects.
Only users with the following permissions can change the Enable Auto-Sync All Executions on New Test Case Version setting in Project Settings:
Project Create – needed to set the option when creating a new project.
Project Modify – needed to update the option in an existing project.
This option is available only for Regular Projects. It does not impact e-Signature enabled Projects.
When you clone a project, the “Enable Auto-Sync All Executions on New Test Case Version” setting is automatically copied from the source project.
General Settings
Go to Project Management.
Click the specific project to access general settings.
Reset 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.
In addition, configure the following features:
Auto Create Values
Auto-create list values during Excel import only if they don’t already exist in QMetry’s system or custom lists.
Note
Keep the flag disabled to prevent adding junk list values in QMetry and maintain clean, defined 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
After creating a project, you can see the Default Resolved Status field on the project settings page.
The Default Resolved Status dropdown shows system default, custom Issue Status, and Jira status values.
By default, Resolved is set as the Default Resolved Status. You 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)
Note
When Jira is not configured with QMetry, the default resolved status will show QMetry Issue status in the drop-down. Select the status to consider issues as resolved.
Archived Issue Status: Archived statuses appear disabled in the “Default Resolved Status” dropdown, but users can still select them to include those issues in reports.
Issues linked across Projects: Records display based on the resolved status settings.
Latest Test Case Execution Status
The latest test execution status gives a quick view of a test case’s performance, helping track progress, identify issues, and assess software quality and stability. It is available in the Test Case list view.
Configure test case execution status for both the - project scope and test case version.
Note
To set the latest test case execution status, enable the “Derive Test Case Execution Status from Test Case Step Status” setting in the project.
You need Project “Modify” permission to change project-level settings.
Test Execution Project Scope
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
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.
Refer to the Execution Status Management to learn how to customize the latest execution statuses of test cases.
Release and Cycle
Add a Release and Cycle to a project for organizing and managing test activities.
Adding Release
During project creation, the system assigns a default release. To add a new release, perform these steps:
Go to the Release and Cycle tab and click + icon.
Select Add Release.
Enter the release name, release start date, and release completion date in the respective fields, then click Add.
Adding Cycles under a Release
Add a new cycle to the project by following these steps:
 |
Click the + icon and select Add Cycle.
A blank row appears for entering cycle details.
Select the release where you want to add the cycle.
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.
Note
You cannot archive or delete the system's default release or cycle.
You with project rights assigned to their role can access the project.
Editing Release and Cycle
Update the release and cycle of a project. These are the steps to edit release and cycle.
Hover the mouse over the field values and the Edit icon becomes visible.
Click the Edit icon and update the values.
Save individual values after editing.
Archiving Release or Cycle
You can archive releases or cycles that are no longer needed
Archiving a release or cycle requires Editing Release or Cycle Permissions.
Deleting a Release and Cycle
Follow these steps to delete a release and cycle:
Archive the Release and Cycle: Click in the Action column of the respective grid to archive the release or cycle.
Confirmation and Archival: After confirmation, the release or cycle gets archived. Archived releases or cycles cannot be edited.
Action Options: Once archived, the Action column displays and for the archived release or cycle.
Delete the Release or Cycle: To delete, click the "Delete" button. Remember, a release or cycle must be archived before it can be deleted.
Note
Archiving a Release, archives all the Cycles under the Release.
Editing a Project
You can modify the project name, description, and reset project settings on the Edit Project page.
To edit a project, follow these steps:
Go to Projects.
Click the project name to open the project detail page.
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
Archive projects that are no longer needed. Archiving does not delete the project or its data; it only hides the project.
Here are the steps to archive a project:
Go to Projects.
Click for the project to Archive.
You can also archive project from project detail page. Open the project detail page and click the Archive icon at the top right corner of the screen.
Note
You need Project "Modify" rights to archive projects, as well as Releases and Cycles.
The system hides Archived Releases and Cycles on the respective lists across all modules.
Once you archive a project, its name no longer appears in the project list.
You cannot edit archived projects.
Cloning a Project
Clone a project to create a new project based on an existing one. After you create it, you can modify the new project independently. You can choose to clone only the folder structure or both the folder structure and associated data.
Note
You need Clone rights to clone a project.
Cloning a project auto-creates the release and cycles in the new cloned project, even if you do not have Create, Modify and Delete Release and Cycle Rights.
To clone a project, perform these steps:
Go to Projects.
Click Clone for the project to clone.
On the project clone screen, the system adds “_copy” to the project name and key by default. You can change these fields if needed.
Select:
Folder Structure: Copies the folder structure along with releases and cycles. It does not copy assets within the folders.
Folder Structure along with Data: Clones project meta-data and requirements, test cases, test suites within folders along with releases cycles.
Click 'Yes' to proceed or 'No' to postpone the action for later.
Note
The amount of time project clone runs depends on the amount of data in the project.
When you start cloning a project, the source project switches to read-only mode, and you cannot perform any actions on it. Therefore, you should run the clone during off-peak hours.
Once you start the clone operation, you cannot stop it.
If cloning fails, the scheduler displays an error.
If cloning gets stuck, the system automatically terminates the job and releases the project lock after 8 hours.
View Scheduled Tasks
Monitor the progress in the notification window on the application header.
The Scheduled Task icon turns Orange in color whenever any of the following actions is initialized:
Click the Scheduled Tasks icon to track following operations:
All bulk operations
Import - IS, TC, TS, RQ
Export - IS, TC, TS, RQ, Test execution
Project clone
Deleting Projects
You can delete a project only after you archive it. Follow these steps to delete a project:
Archive the project.
Select the Show Archived check box on the Project list view.
Click the cog icon for the archived project and select .
Unarchiving a Project
To unarchive a project, follow these steps:
On the Projects screen, select Show Archived.
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 assign permissions. You can access the project based on their assigned role.
To manage users for a project, follow these steps:
Go to Projects and click the project name.
Go to the Users tab to view all user details associated with the project.
To view the list of available users, click .
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 users and click .
Perform the following operations:
Add a New User: Click the Create New User link located beside the Link button.
Remove User Role Mapping: Click Unlink next to the user.
Unlink Multiple Users: Select the desired users in the grid and click the .