Project Permissions Impact | SolDevelo Documentation

Project permissions and their settings affect the use of the QAlity Plus app. Incorrectly configured, they can lead to a situation where the user cannot perform a certain action related to the app.

Even if you're a Jira Admin, it doesn't mean you have all the required permissions for a project, which can cause problems when using the app.

It’s important to understand how a given permission affects a function in the app. Therefore, the most common cases are listed in the table below, showing how the absence of certain permissions impacts functions in the app.

The most common cases reported by our clients

Problem

The user in the Test Cycle Overview panel tries to view the Test Cycles from a given project, but nothing is shown to them (Request failed with status code 400).
The user cannot create a test case, for example, from the Test Case Repository page or in the work item Jira (The Jira server was contacted but has returned an error response. We are unsure of the result of this operation. Close this dialog and press refresh in your browser).
The user cannot add test steps to an existing test case (the button is grayed out).
The user has different user groups in a Team Managed project - the internal team and the client’s team. The client's team is not able to manage and edit test cases.
The user would like to link the test case to the selected requirements (e.g., Story), but does not see such an option in the list under the +Add button.

Solution

No Browse Project permission in the project the user is trying to filter.
No Create Issues permission for the project where the user attempted to create a test case.
No Edit Issues permission in the project where the test case was created.
The client's team members are marked as View role in the Project Settings instead of Member role, which includes Edit Any Issue permission.
No Link Issues permission in the project where the user links the test case.

Table of permissions and their impact on QAlity Plus

This part presents the matrix of the impact of disabling a given permission occurring in QAlity and QAlity Plus depending on the given page/subpages or the roles played in the project (divided into project types). Cloud (Company-managed software) projects and server: (Business and Software) projects. Before you start analyzing the table, please take a look at the video explainer and read the legend below.

Legend:

🔴 - When a given permission is restricted, it means actions cannot be performed by the user.

🟢 - When a given permission is restricted, it means actions can be performed by the user.

🟠 - When a given permission is restricted, it means some actions can be performed by the user and some cannot. The description contains a detailed explanation.

Pages/'Subpages'	No browse ‘projects’ permission	No create ‘issue’ permission	No edit ‘issue’ permission	No create attachments permission	No delete All attachments permission
Jira issue view/QAlity issue type	n/a	🟠 Description 🟢 The user can: edit the test case name add/edit/delete steps delete other attachments execute test case from the different project in test cycle from project without browse permissions 🔴 1. The user cannot create a test case. 🔴 2. The user cannot add attachments - to add an attachment in a test case, the user must have create ‘issue' permission and create 'attachments’ permissions.	🔴 Description The user cannot: add a new test case edit the test case name add/edit/delete steps add attachments - to add an attachment, the user must have two permissions: edit permission and create attachments permission. delete other attachments - to remove an attachment added by other users, the user must have two permissions: edit permission and delete all attachments permission. The user cannot execute with: test case menu (lack of execution option) test case panel => execute => a flag appears	🔴 Description The user cannot add an attachment to the test case. To add an attachment in a test case, the user must have create permission and create attachments permissions.	🔴 Description The user cannot delete attachment to the test case. To remove an attachment added by other users, the user must have two permissions: edit permission and delete all attachments permission.
Execution page	🔴 Description Execution is not available for the user.	🟠 Description 🟢 The user can: assign user or change status, add/edit comment, delete other attachments, link/unlink a bug, delete the execution. 🔴The user cannot: Add attachments - to add an attachment in a test case, the user must have create permission and create attachments permissions. Create a bug related to Regression - no create permissions project.	🔴 Description The user cannot: Assign user or change status. Add/edit comments, Add attachments - to add an attachment, the user must have two permissions: edit permission and create attachments permission. Delete other attachments - to remove an attachment added by other users, the user must have two permissions: edit permission and delete all attachments permission. Create/link/unlink bugs. Delete the execution.	🔴 Description The user cannot add an attachment to the test case. To add an attachment in a test case, the user must have create issue permission and create attachments permissions.	🔴 Description The user cannot delete attachment to the test case. To remove an attachment by other users, the user must have two permissions: edit permission and delete all attachments permission.
Execution history page	🔴 Description The user doesn't have access to the issue, therefore they cannot enter Execution history.	🟢 Description The user can go to the execution history page and Go to the execution page by execution history page The user can delete the execution.	🟠 Description 🟢 1. The user can go to the execution history page 🟢 2. Go to the execution page of a test case that does not have edit permission through the execution history page. 🔴 The user cannot delete the execution.	n/a	n/a
Test cycle Overview page	🔴 Description Project filer: the selected project won’t be visible on the project filter. Create test cycle modal - project filter: the selected project won’t be visible on the project filter.	🟠 Description 🟢 The user can close/reopen and delete the test cycle. 🔴 1. Create test cycle modal - project filter: The selected project won’t be visible on the project filter. 🔴 2. Clone test cycle: The user cannot clone the test cycle.	🟠 Description 🟢 The user can enter the test cycle, but 🔴They cannot clone/delete/close/reopen the test cycle.	n/a	n/a
Test Cycle Details page	🔴 Description The user has no way to enter the page. The Test Cycle Details page won’t be visible for the test cycle from the project without browse permissions.	🟠 Description 🟢 The user can: open the test case execution, add test cases to the test cycle edit the test cycle name, delete/close/reopen test cycle, delete test cases from test cycle, Dnd test case, assign user to execution and change statuses. 🔴 The user without create permission cannot clone the test cycle.	🔴 Description The user cannot: open the test case execution, add test cases to the test cycle, edit the test cycle name, clone/delete/close/reopen test cycle, delete test cases from test cycle, Dnd test case, assign user to execution, user cannot change the execution status of a test case for which they don’t have edit permission.	n/a	n/a
Execution report page	🔴 Description The selected project won’t be visible on the project filter.	n/a	n/a	n/a	n/a
Traceability report page	🔴 Description Project filter: The selected project won’t be visible on the project filter. Linked bugs: If the execution of a given test case is linked to a bug from a project without browse permission, the user won’t see what kind of ticket it is.	n/a	n/a	n/a	n/a
Test Case Repository page - all test cases	🔴 Description Project filer: 1. The selected project won’t be visible on the project filter. Test case menu/bulk bar - Add test case to folder/subfolder: 2. The selected project won’t be visible on the select folder modal. Bulk bar: 3. Add to test cycle: The selected test cycle won’t be visible for the project without browse permission. a. Create a new test cycle: The user cannot create a test cycle for this project. Display folder/subfolder on side menu: 4. If the Admin creates a folder in which the main project is selected without browse permission for the Regular user, then the regular user won't see this folder/subfolder in the side panel. Create a folder/subfolder 5. Side menu/bulk bar: the selected project won’t be visible on the project filter.	🟠 Description Project filer: 🟢 1. the selected project will be visible on the project filter. Test case menu/bulk bar - Add test case to folder/subfolder: 🟢 2. the selected project will be visible on the select folder modal. Bulk bar: 🟢 3. The user can add any test case to that folder/subfolder. Display folder/subfolder on side menu: 🟢 4. If the Admin creates a folder in which the main project is selected without create permission for the Regular user, then the regular user will see this folder in the side panel. DnD 🟢 5. The user can dnd test case to the folder/subfolder with create permissions. Create folder/subfolder (side menu/bulk bar): 🔴 1. The user cannot create a folder/subfolder. Bulk bar: 🔴 2. The user cannot create a test cycle using the bulk bar Create Test Case: 🔴 3. The user cannot create a test case while clicking the button.	🟠 Description Project filer: 🟢 1. the selected project will be visible on the project filter. 🟢 2. The user can create a folder. Display folder on side menu: 🟢 3. If the Admin creates a folder in which the main project is selected without edit permission for the Regular user, then the regular user will see this folder in the side panel. 🔴 Test case menu/bulk bar - Add test case to folder/subfolder: 1. The user cannot add test case by menu/bulk bar to folder the selected project won’t be visible on the folder (the user doesn’t have edit permission for the main project folder) 🔴 DnD 2. The user cannot dnd a test case to the folder/subfolder without edit permissions.	n/a	n/a
Test Case Repository page Repository - folder view	🔴 Description The same as Test Case Repository page - all test cases.	🟠 Description 🟢 1. Project filter: The selected project will be visible on the project filter. 🟢 Delete a test case from a folder/subfolder 2. The user can delete a test case from the folder/subfolder without create permission. 🟢 Create a test case in a folder/subfolder 3. The user can create any test case in this folder but 🔴 cannot create a test case for the selected project without create permission.	🔴 Description 🔴 Create test case in folder/subfolder 1. The user cannot create a test case in this folder. 🔴 DnD 2. The user cannot dnd test case to the folder/subfoler without edit permissions.	n/a	n/a
Dashboard page	🔴 Description The selected executed test case won’t be visible on the entire page.	🔴 Dsecription 🔴 1. Create test cycle modal - project filter: the selected project won’t be visible on the project filter.	n/a	n/a	n/a
Bulk test case page	🔴 Description The selected project won’t be visible on the project filter.	n/a	🔴 Description The user cannot select project without edit permissions.	n/a	n/a
Import page	🔴 Description The selected project won’t be visible on the project filter.	🔴 Description The user cannot import test cases to that project.	n/a	n/a	n/a
Export page	n/a	n/a	n/a	n/a	n/a
QAlity settings page	🟢 Description Jira admin has access to this page and will see the project without browse permissions.	n/a	n/a	n/a	n/a
Test Case Execution Status Scheme	🟢 Description The lack of browse permission does not affect access to this page, provided you are a Jira admin.	n/a	n/a	n/a	n/a
Test Type page (Plus Advanced version)	🟢 Description The lack of browse permission does not affect access to this page, provided you are a Jira admin.

Cloud: Team-managed software projects.

Legend:

🔴 - When a given permission is restricted, it means actions can not be performed by the user.

🟢 - When a given permission is restricted, it means actions can be performed by the user.

🟠 - When a given permission is restricted, it means some actions can be performed by the user and some cannot. The description contains a detailed explanation.

Project Access	No defined role	Viewer	Member	Administrator
Private	🔴 Description The user with no defined role can not view, add, edit and delete in that project. The user does not have access to project settings.	🟠 Description 🟢 The user with a role defined as Viewer can view but 🔴 cannot add, edit, or delete in that project. 🔴 The user also does not have access to project settings.	🟠 Description 🟢 The user with a role defined as Member can view, add, edit, and delete in that project. 🔴 The user does not have access to project settings.	🟢 Description The user with a role defined as Administrator can view, add, edit, and delete in that project. The user has access to project settings.
Limited	🔴 Description The user with no defined role can not view, add, edit and delete in that project. The user does not have access to project settings.	🟠 Description 🟢 The user with a role defined as Viewer can view but 🔴 cannot add, edit, or delete in that project. 🔴 The user also does not have access to project settings.	🟠 Description 🟢 The user with a role defined as Member can view, add, edit, and delete in that project. 🔴 The user does not have access to project settings.	🟢 Description User with a role defined as Administrator can view, add, edit and delete in that project. User have access to project settings.
Open	🟠 Description 🟢 The user with no defined role can view, add, edit, and delete. 🔴 The user does not have access to project settings.	🟠 Description 🟢 The user with a role defined as Viewer can view but 🔴 cannot add, edit, or delete in that project. 🔴 The user also does not have access to project settings.	🟠 Description 🟢 The user with a role defined as Member can view, add, edit, and delete in that project. 🔴 The user does not have access to project settings.	🟢 Description User with a role defined as Administrator can view, add, edit, and delete in that project. User have access to project settings.