Our documentation site has been updated to AIO Tests Knowledge Base

Project Permissions

Owned by Noopur Varshney [AIO Tests]
Last updated: Feb 14, 2023
4 min read

AIO Tests allows users to specify operation level permissions giving them the ability to control who can perform what actions in AIO Tests. These permissions can be applied to active Jira users as well as Jira Groups. The permissions set for one project do not have any impact on AIO Tests operations for other projects. This article explains the permissions as well as its usage and impact.

  • By default, users having access to a Jira project can perform all operations in AIO Tests

  • Only Jira & Project Admin & designated AIO Admins have access to setup permissions for a project

Please note the Group based access (Apps → Manage Apps → AIO Tests → Access) is the first governing access for groups. Permissions set at project level for Jira Groups do not override the access specified for those groups at the global level.

Accessing Permissions page

To setup permissions for users/groups, go to Project Settings from the cog icon and click on Permissions from the left panel.

 

Understanding and Setting up Permissions for Users & Jira Groups

Understanding Permissions

Entity

Permissions

Description

Entity

Permissions

Description

Cases

Create/Edit

Ability to create and edit cases from different screens of AIO Tests

 

Delete

Ability to delete cases from AIO Tests

Sets

Create/Edit

Ability to create and edit sets in AIO Tests

 

Delete

Ability to delete sets from AIO Tests

Cycles

Create/Edit

Ability to create cycle and edit cycle details in AIO Tests

 

Delete

Ability to delete cycles from AIO Tests (Adhoc Cycle cannot be deleted since it is a system defined cycle)

Cycle Cases

Add

Ability to add cases in a cycle for execution

 

Remove

Ability to remove/delete cases from a cycle

 

Execute Cases

Ability to execute cases (status, timer, defects, attachments, etc.) and add runs to a case in a cycle

 

Lock Cycle

Ability to lock cycle so that no further changes can happen in the cycle

Others

Contact AIO Support

Ability to contact AIO Tests Support via the icon on the top

 

Edit Project Settings

Ability to set up additional users as Admins so that they can setup Project Settings

Setting up Permissions

By default all users having access to the project can perform all actions. AIO Tests gives the ability to specify permissions for active Jira users as well as groups created in Jira. Group permissions are applied to all users belonging to that group. AIO Tests offers three options to setup permissions - All (default), Include and Exclude.

 

  • Include: Only Users/Groups specified with Include access can perform the action on which this access is set. Everyone else is automatically excluded which means they cannot perform the specified action

  • Exclude: Users/Groups specified with Exclude access cannot perform the action on which this access is set. Everyone else can perform the specified action

  • All: All users having access to the project can perform the specified action

Below is an example wherein AIO Testing Jira group (users belonging to that group) and Noopur Varshney are the only folks that can delete cases from this project in the system. Everyone else is automatically excluded from deleting cases.

Groups and users are in their separate columns

 

Impact on different screens of AIO Tests

Following screens are impacted once specified permissions are set

Permission

Impact

Permission

Impact

Exclude Create/Edit Cases

Excluded users cannot create/edit case from

  • Create Case button

  • Create new case from Set

  • Create new case from Cycle

  • Create new cases via import

  • Create new cases via automation results import (UI & API)

  • Edit case from Cases grid and from Edit on Case Details page

  • Edit case from cycle

Exclude Create/Edit Sets

Excluded users cannot create/edit set from

  • Create Set button

  • Edit Set details from Sets grid and from Set Details page

  • Move sets in folders

Exclude Create/Edit Cycles

Excluded users cannot create/edit cycle from

  • Create Cycle button

  • Copy cycle button

  • Create cycle via Jenkins/automation setup

  • Edit Cycle details from Cycles grid and from Cycle Details page

  • Move cycles in folders

Exclude Add Cases

Excluded users cannot add new cases to a cycle

  • while creating a cycle

  • while editing a cycle

  • from Manage Cases → Create new case and Add existing cases

Exclude Remove Cases

Excluded users cannot remove cases from an existing cycle

  • while editing a cycle

  • from Manage Cases → Bulk Remove cases

    • using the remove case icon on each case row

Exclude Execute Cases

Excluded users cannot

  • change status of a case in the cycle

  • add defects to a case

  • add comments to a case

  • add attachments to a case

  • add runs to a case

  • edit case from a cycle

Exclude Lock cycle

Excluded users cannot lock a cycle
(Lock option is available under Manage Cases button on cycle details page. Locking cycle details can be found here)

Exclude Contact AIO Support

Excluded users cannot contact AIO support (won’t see the contact us button)

Include Edit Project Settings

Included users can access Project Settings page in Edit mode apart from the Jira and Project Admins

Example

Below is an example of sample setup.

  • Testers group can create/edit cases and execute cases but they cannot add/remove cases to a cycle. Testers cannot create cycles or sets as well. Testers cannot delete cases/sets/cycles

  • Managers group can Lock cycles and do all actions that testers cannot