Our documentation site has been updated to AIO Tests Knowledge Base

Project Settings

The Project Settings area allows users to customize AIO Tests app to suit their own process and personalize the app based on how their organization works.
This interface will continue to grow with our upcoming releases.

This article covers the access of settings page and talks briefly about the available customizable options.

Accessing Project Settings

Project Settings page is accessible to all but only Jira and Project Admins can perform the available actions or if the Admins have assigned other users as AIO Admins. The page is available via the cog icon on top right.

 

Below you can see the two views - Admin and non-Admin.

Admin View

Non-Admin View

Field Configurations

Users can customize the screen for Cases, Sets and Cycles by enabling/disabling fields available while creating entities from here. Users can also mark certain fields as mandatory.

Case Types

Users can customize the available case types that are provided by default in the system. New Case Types can be added, existing ones can be updated, archived or deleted. The order in which the types appear in the Type drop-downs can also be managed from here.

Case Statuses

Users can customize the available case statuses that are provided by default in the system. New Case Statuses can be added, existing ones can be updated or deleted as long as a few rules are satisfied (discussed in detail here). The order in which the types appear in the Status drop-down can also be managed from here.

Case Priorities

Users can customize the available case priorities that are provided by default in the system. New Case Priorities can be added, existing ones can be updated, archived or deleted. The order in which the priorities appear in the Priority drop-downs can also be managed from here.

Disable AIO Tests

Users can disable AIO Tests on a project. Users can also control who has the access to enable AIO Tests on a project.

Group Based Access to AIO Tests

AIO Tests allows users to setup access to AIO Tests based on groups in Jira. If you have marketing, sales, etc. folks using Jira along with Dev and Testing teams, AIO Tests can be made accessible to only Dev and Test teams.

Custom Fields

AIO Tests allows users to define 10 different types of custom fields in order to track their process more efficiently. Here are the different types - Boolean, Number, Date, Single line text, Single select list, Multi select list, Single user selector, Multi user selector, URL, Multi line text - RTF.

General Preferences

AIO Tests allows users to specify the default issue type to use while creating bugs/defects from cycle details page of AIO Tests. They can also specify AIO fields that should be part of the description of the defect being created.

Report Preferences

AIO Tests allows users to customize the Defect Pie graphs in Single and Multi cycle execution summary reports. They can choose the Jira Field on which the Pies should be generated.