Roles

A user role defines user’s capability to access the modules and carry out functions under the role rights. Admin, QA Manager, Read only, and Tester are the default roles provided by QMetry.

As QMetry Admin, you can create roles in addition to the mentioned default roles. Once you are done with creating roles, you can assign the roles to individual QMetry users when they are added to QMetry Projects.

On login, you can view only those modules that are permitted to your role. In case of features, they appear disabled if the role assigned does not have any permissions for it.

Creating a User Role

  1. Expand Customization and select Roles on the side bar.

  2. Click New on the top right corner of the screen.

    QPro_Customization_Jira_New
  3. It opens the Create Roles screen with fields to create a new role. Enter the following details:

    • Role Title: Enter name of the user role.

    • Role Description: Enter description of the user role.

    Make this the default role for new LDAP/SAML users: Select the check-box to make the role to be assigned by default to every new LDAP/SAML user for the Project.

Module Permissions

Permissions available if Customization App is enabled

The matrix of Modules and Rights are available on the screen. Admins can choose to provide selective rights for the different modules.

Permissions

Implications

View

It allows you to view the module.

Create

It allows you to create new records for the module.

Modify

It allows you to update the details of the module. Archive or Unarchive folder and asset permissions are included under modify rights.

Delete

It allows you to delete the records of the module.

Execute

It allows you to execute test case and test suite.

Import

It allows you to import entities like requirement, test case, test suite and issue.

Export

It allows users to export entities like requirement, test case, test suite and issue.

Link

It allows you to link entities like requirement, test case, test suite and issue.

Copy

It allows you to copy entities like requirement, test case, test suite and issue.

Versioning

It allows you to create and manage versions of requirement and test case.

Admin can also choose to Apply or Clear all rights using the following buttons.

  • Apply All Rights: Assign all rights of all modules to the Role at once.

  • Clear All Rights: Unselect the selected Permission check boxes in one go.

    Note

    The permissions are assigned to a Role. It means all the users with that role for that project will have similar rights over the modules.

QPro_Customization_Jira_Assigned_role

Test Suite Execution and Modification:

  • With Execute Permissions:

    With "Execute" test suite permissions, you can:

    • Execute the test suite.

    • Modify the assignee and planned date, either before or during execution.

    However, you cannot alter any other details related to the test suite. This setup ensures that testers can self-assign executions and plan their executions accordingly.

  • With Test Suite Modify Permissions:

    With "Test Suite Modify" permissions, you can:

    • Modify test suite details.

    • Update the execution assignee and planned date on the Test Suite Execute page.

    You cannot execute the test cases but can assign testers and plan executions as per the release schedule.

User module: The following rights are made independent of each other. The control settings for deactivating the users are kept separate so that the teams can create users without the control of deactivating any existing user.

  • Create or Update

  • Activate or Deactivate

  • Delete

Project module: The following rights are independent of each other. These granular rights ensure that Create/Modify/Clone/Delete rights can be allocated separately only to the relevant users who need those permissions.

These rights are related to Project only. Release and Cycle rights are regulated separately.

System admin can regulate project admin permissions.

  • Project Create: You can create a new project.

  • Project Modify: You can Modify and Archive Project.

    • You can assign User roles in projects.

    • You can integrate Source Code Repository, rename Projects, and change other project settings.

  • Project Clone: You can clone only those projects that are assigned to you.

  • Project Delete: You can delete only those projects that are assigned to you. This permission does not apply to the deletion of the release and cycle.

Release/Cycle:

QPro_Customization_Jira_Release_cycle

System admin can regulate Release and Cycle permissions as follows -

  • View - View rights enables you to view Releases and Cycles.

  • Create - Create allows creating Release and Cycle for a particular project.

  • Modify - Modify allows modifying the Releases and Cycle and archiving the Release and Cycle.

  • Delete - Delete allows deleting the Releases and Cycles.

Automation: Users with “Modify” rights can import automation results and create assets in QMetry. It allows you to configure and use QMetryAutomation Agent to schedule and trigger the execution.

To generate the Automation API Key, users should have Automation “Modify” and Integration “Modify” rights.

Integration: “View” rights enables you to view Integration and Jira Scheduler Status. With “Modify” rights, you can integrate the external trackers with QMetry projects, map external tracker issue types with the QMetry Requirement or Issue module, configure custom Jira fields for QMetry modules, and sync Jira issues and/or its project metadata.

Report: QMetry System Reports module is visible only if you have “View” rights for Report. Similarly, you can make any changes within the module only if they have the “Modify” rights for the Report.

Admin Report: Login Summary Dashboard and Gadgets are accessible if you have the “View” rights for Admin Report. You can make changes in the reports if you have the “Modify” rights for the Admin Report.

Permissions

Implications

View

You can do the following:

  • See the Login Summary Dashboard and Gadgets.

  • See shared dashboard containing Login Summary Dashboard and Gadgets.

  • Only share the Login Summary Gadgets.

  • Schedule and export dashboards with Login Summary Gadgets.

Modify

  • Users can create or modify custom dashboards to add all Login Summary Gadgets.

QMetry Insight: With “View” rights, you can view Custom Gadgets. With “Modify” rights, you can write custom queries in QMetry and save them as gadgets. It allows you to modify created custom gadgets.

Report Module Rights

QMetry Insight Module Rights

View

Modify

View

Modify

Permissions

Y

N

NA

NA

You can view System reports and shared dashboard.

Y

Y

NA

NA

You can view System reports, create custom dashboard and view shared dashboard.

NA

NA

Y

N

You can view Custom Gadgets.

NA

NA

Y

Y

You can write custom queries in QMetry and save them as gadgets.

Modify right allows you to modify your created custom gadgets.

Report Module Rights

QMetry Insight Module Rights

View

Modify

View

Modify

Y

N

NA

NA

Y

Y

NA

NA

NA

NA

Y

N

NA

NA

Y

Y

CICD Rule:

  • View: With only “View” permission for the CICD Rule module, you can just view the CICD module but cannot perform any action.

  • Modify:

    • Manage: With “Manage” permission for the CICD Rule module, you can add and edit the CICD Rules configuration.

    • Delete: With “Delete” permission for the CICD Rule module, you can delete the configured CICD Rules.

    • Execute: With “Execute” permission for the CICD Rule module, you can execute the configured CDCD Rules.

QMetry Intelligent Search:

Permission

Implications

View

With only “View” permissions for QI Search , you can just view the Project Documentation Configuration.

Modify

With the QI Search “Modify” permissions, you can configure the project-specific documentation for AI search.

Flaky Score:

  • View: It allows you to view Flaky Score configuration.

  • Generate: It allows youto generate the Flaky Score. Admin and QA Manager roles have this permission by default.

  • Modify: It allows you to modify the configuration for generating the Flaky Score. Admins have this permission by default.

Success Rate:

  • View: It allows you to view the Success Rate configuration.

  • Generate: It allows you to generate the Success Rate. Admin and QA Manager roles have this permission by default.

  • Modify: It allows you to modify the configuration for generating the Success Rate. Admins have this permission by default.

    QPro_Customization_Jira_Modify

Once you have allocated the rights, click Create to create the user role with the permissions.

Permissions if Customization App is Disabled

Admin can assign "View" and "Modify" rights for the following modules:

  • Requirement

  • Test Case

  • Test Suite

  • Issue

The matrix of Modules and Rights are available on the screen. Admins can choose to provide selective rights for the different modules.

Permissions

Implications

View

It allows you to view the module.

Modify

It allows you to update the details of the module.

Admin can also choose to Apply or Clear all rights using the following:

  • Apply All Rights: Assign all rights of all modules to the Role at once.

  • Clear All Rights: Unselect the selected Permission check boxes in one go.

    Note

    The permissions are assigned to a Role. It means all the users with that role for that project will have similar rights over the modules.

QPro_Customization_Jira_Basic_role

After allocating the rights, click Create to create the user role with the permissions.

Editing User Roles

  1. Expand Customization and select Roles on the sidebar.

  2. Click Edit for the role to edit.

  3. Make the required changes and click Update.

Deleting User Roles

  1. Expand Customization and select Roles on the side bar.

  2. To delete a user role, click Delete.

Publication date: