Custom Fields

Sometimes users need additional fields to track their organization’s testing process. AIO Tests allows users to define custom fields allowing them to personalize AIO Tests to their needs and track details at a more granular level.

Custom Fields in AIO Tests is project specific and is currently available for Cases, Sets, Cycles and Runs. Once created, data for custom fields can also be imported while importing cases and cases with custom fields can also be exported. Custom fields can also be marked as required fields.

Creating a Custom Field

Listed below are the types of custom fields that can be created in AIO Tests.

1. Boolean: Allows users to define a yes/no type of field

2. Date: Allows users to define a date field

3. Number: Allows users to define a number field

4. Single line text: Users can enter a single line of text in this field

5. Single select list: Users can choose a single value from a list of options

6. Multi select list: Users can choose multiple values from the provided list

7. Single user selector: Users can pick one user from the list and also select if the user should be notified via email

8. Multi user selector: Users can pick multiple users from the list and also select if the users should be notified via email

9. URL: Users can enter URLs that can point to confluence requirements, google drive documents, etc.

10. Multi-line text (RTF): Text can be entered on multiple lines using RTF for this type of field

11. Jira Field: Users can bring in their single-select Jira fields in AIO Tests along with Sprint information

To create a custom field, follow the steps below:

1. Click on gear icon and select Project Settings. Select Custom Fields from the left panel

   Open

   

    

2. Click on the ‘+' sign to open the custom field entry screen. Name is a mandatory field. By default, in the Type drop-down, Boolean will be selected. Users can change the type of custom field using the highlighted down arrow. Users can click on the highlighted 'Save’ button to save the newly created custom field

   1. Name - Name of the field to be created

   2. Description - Description of the field to be created

   3. Type - Type can be anyone of the above described types

   4. Applies To - Select the entity for which the field is being created

   5. Required - Check the box if the field is required for any entity

   6. Allowed List Values - This is applicable for Single select list and Multi select list. Define the values from which the users can choose

   7. Default Values - Enter values in the space so that when the entity is being created the default value will be entered automatically. Users will have the option to change it upon entity creation

   8. Notify User - This is applicable only for ‘Single user selector’ and ‘Multi-user selector’ options. Users can choose if the person should be notified via emails about them being added to this field
      
      

      Open

      

       

       

Custom Fields for Sprint and Jira Custom Fields

AIO Tests supports creating custom fields mapped to single select custom fields and Sprint fields in Jira.

1. Users can create a new custom field and select Jira Field from the Type dropdown. This would fetch all Jira fields applicable to the Issue Screens in Jira along with Sprint (if applicable in project).
   
   

2. Select the Jira field to map to. Set a name and select the entities the custom field applies to. Values are populated from Jira. In case of Jira custom field, applicable values to current project are displayed. In case of Sprint, sprints applicable to boards of current project will be shown.

    

3. Select default values if required and mark them as mandatory, based on need.

4. Save the custom field. Once created, the Jira based custom fields would continue to work as other custom fields and should be available in filters, columns, export, import, copy of cases etc.

Custom Fields for Runs

Users can also define custom fields at the Run level to capture details while execution e.g. Browser, Environment, Build Numbers, etc.

If the field is marked as mandatory, users will get the option to specify on which status the validation should be triggered. Read here on how to access them.

Accessing Case, Set and Cycle Custom Fields

Once fields are created, they will be available as a separate section in each of the entities. The image below shows how the newly added fields appear on ‘Create Case’ screen. It will similarly appear on Create Set, Create Cycle and corresponding Edit screens.

Right panels

The Custom fields also appear on the right panels of all entities as shown below (shown for Cycle).

Accessing Run Custom Fields

The custom fields defined for Runs are only available on the Execution tab within the Cycle Details page. They can be edited using the pencil icon next to the heading.

If the fields have been marked as mandatory, validations will be triggered on the corresponding status change (as well as bulk status change).

The custom fields can be updated for multiple runs together using the ‘Bulk edit latest runs’ option from Manage Cases ellipsis. Validations will be triggered based on the status selected and setup.

Editing a Custom Field

To edit a custom field, go to Project Settings → Custom Fields and click on the edit icon next to the field. The field values will become editable. Users can change the name, applicable entity, default values and allowed list values.

Deleting a Custom Field

A custom field can be deleted from the system if it doesn’t have any associated values in any of the entities using the delete icon.

Custom Fields Available for Viewing and Sorting in Lists (grids)

Most of the custom fields will be available to be added in the lists view on all entities via the Column Selector.

Once the field is added to the grid view, users can sort on the custom fields by clicking on the header.

Custom Fields Available for Filtering

Once the fields have been added, they are available in the list of filters. Users can filter on these fields even if they are not added to the grid view.

Reserved Names

To avoid confusion with AIO Tests default fields, certain names have been reserved and thus users cannot create custom fields with names same as the reserved names. Below is the list.