Required Permission: Jira users with the Administer Project and Browse Projects permissions for the project can configure QMetry permissions for that project.

Administrators can enable QMetry permissions to manage user access for different modules like Test Case, Test Cycle, Test Plan, Configuration, Exploratory Testing, Import, Export, and so on.

The QMetry permissions for the project are disabled by default. All the users who can view the project will be able to perform any operations in QMetry for that project. After enabling permissions, all permissions are assigned to All Users by default. Permissions can be assigned to users, groups, or everyone.

For a team-managed project, if the Administrator does not have permission to the team-managed project (in case of private access), they will not be able to enable/disable permissions.

1 Steps to Enable QMetry Permissions
2 Module wise Permissions
- 2.1 Test Case
- 2.2 Test Cycle
- 2.3 Test Plan
- 2.4 Configuration
- 2.5 Exploratory Testing
- 2.6 Report
- 2.7 Requirement
- 2.8 Defect
- 2.9 Import - Export
- 2.10 QMetry Intelligence
3 Sync Permission

Steps to Enable QMetry Permissions

Perform the following steps to enable QMetry Permissions:

From the Projects drop-down list on the Jira main menu, select the project for which you want to enable the QMetry Permissions.
Click the Project Settings on the navigation bar.

3. On the Project settings page, click QMetry Permissions on the navigation bar.

4. On the Permissions screen, enable the Permissions on the Permission tab to enable configuration setup for different modules. The Permissions flag remains disabled by default.

Once the Administrators enable the Permissions option, the screen displays Module wise permissions.

The permissions are assigned to all by default.

Module wise Permissions

Administrators can assign Module wise permissions to users and groups. Refer to the following table for the description on permissions:

Permissions	Implications

Permissions	Implications
View	It allows users to view the module.
Create	It allows users to create new records for the module.
Edit	It allows users to update the details of the module.
Delete	It allows users to delete the records of the module.
Test Cycle Execute	It allows users to execute the Test cycle.
Import	It allows users to import test cases.
Export	It allows users to export entities like test cases.
Versioning	It allows users to create and manage versions of the Test Case.
Manage Folders	It allows users to create and manage folders of the Test Case, Test cycle, and Test Plan.

Test Case

The testers in the team require test case permissions to perform Test Case related operations.

In the case of Automation, users with Test Cycle Create rights can create test cases through automation even if they do not have Create rights for the Test Cases.

Test Cycle

The testers who are executing test cases require Test Cycle permissions.

In the case of Automation, users with Test Cycle Create rights can create test cases through automation even if they do not have Create rights for Test Case.

Test Plan

QA Managers require Test Plan permissions to perform the operations on Test Plans.

Configuration

If the user has View rights for Configuration, then they can only view the Configuration settings of the project. The user can also generate the Open API key and the Automation API key.

If the user has Modify rights, then they can change the Configuration. For example, Add, Edit, Delete custom fields, labels, components, execution results, updating preferences, and so on.

Exploratory Testing

The testers and Business Analysts in the team require Exploratory Testing permissions.

Report

QA Managers require Report permission.

Requirement

The testers and Business Analysts require Requirement permission.

Linkages of test case with the story: If the user has Edit rights of Requirement, then they can link or unlink test cases with the story. If the user has View rights, then they can only view the linkages.

Defect

QA and Development teams require Defect permission.

Defect Traceability when the user has the View rights: The user can view the linkages of the test cases with Story issue, the associated bug on the Test Cycle Execution screen and view the Bug detail page in Jira.
Defect Traceability when the user does not have View rights: The user can view the associated bug on the Test Cycle Execution screen but they can not view the Bug traceability panel details on the Jira issue page.

Import - Export

The testers in the team require Import and Export permissions to import and export test cases.

Import Test Case: If users need to Import Test Cases, they need to have all rights under Test Case and Configuration sections enabled along with Import permissions.

We need to provide Export access in the case when the user wants to export Test Assets into an excel sheet:

QMetry Intelligence

To modify the configuration and to calculate the Flaky Score and Success Rate, the users must have the relevant permissions of QMetry Intelligence section.

Modify the Search configuration for “Ask me Anything”: To modify the configuration of Project documentation, the users must have the following permissions in the QMetry Intelligence section.

Change the Default "Assign to All" Permission

By default, all the users will have respective permissions as the Assign to All is checked.

To edit a permission, remove the selection of Assign to All checkbox. The permission record appears in editable mode.

To grant the permissions to the users, open the Users drop-down list and select users.

To grant the permissions to the groups, open the Groups drop-down list and select groups.

This way you can add or edit permissions to users or groups for each module.

Sync Permission

Sync Permissions with Jira Permissions and Jira User Groups:

The changes made in Jira permissions, Jira users, and Jira user groups do not sync immediately in QMetry.

The Sync Permission will sync these permissions for the following actions:

Addition or Removal of Jira permission. For example, Browse Project.
Addition of users in Jira Groups
Removal of users from Jira Groups
Deletion of Jira Groups
Deletion of user

Users' permission within the group in QMetry for Jira plugin will be impacted only after Syncing the permission.

View the Progress of Permission Sync

To view the status of the background process of permission sync, click on the Bell icon at the top.

The Notifications pane opens. It displays the progress of the sync process.

QMetry Permissions for Project