Role management is the role a user is assigned to within a project. At the project level, Role asserts the level of access the user can have within a project.
A user can have
all or none or a combination of Add/Edit, Delete, Import, Export access for Releases, Test Cases, Test Case Modules, Test Runs, Test Results, Reports, Issues, Requirements and Integrations.
two types of roles on the basis of whether they are pre-built or not.
1.System Role 2.Custom Role
These are the default roles already available for selection within the QA Touch platform.
3 types of system roles.
1.Full access 2.Basic Role [view access] 3.Developer
The Full Access role grants complete access of the project to the user who are assigned with the access.
The user with
full access will be able to view, edit and delete the elements within a project such as test cases, test runs, releases and issues.
The user with
access to Basic Rolewill have only view access the elements within a project such as test cases, test runs, releases and issues.
The user with this role
will not be ableto edit or delete these elements.
A user assigned Developer Role will
only have access to Issues section. They can create and view issues within a project and change the status of issues.
won’t be able to access any other feature in QA Touch.
This is a
user defined role. Using this feature, you can assign
1.Add/Edit 2.Delete 3.Import and Export access to individual features like Releases Test Cases, Test Runs, Reports, Test Results, Issues, Integrations and Requirements within a project.
image shows Creating a Custom Role and providing user defined feature level access.
image shows the custom user defined access the user with the custom role (created in above image) has for each feature within a project.