Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

AIO Tests allows users to create new custom fields for cases, sets, cycles , and runs with ease. It enables them to personalize AIO Tests as per their requirements and track details at a more granular level. Custom Fields in AIO Tests are project-specific and are 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. Users can also mark the custom fields as required fields. On the test management tool, users can edit the custom fields and delete them as per their organization’s needs. 

Info

Only Jira Admins, Project Admins and designated AIO Admins can add/edit/delete custom fields in the project.

In this documentation, you’ll understand:

Table of Contents
minLevel1
maxLevel6
outlinefalse
stylenone
typelist
printablefalse

Steps to Create a Custom Field

...

Once you click on the Save button, the Jira-based custom fields will continue to work as other custom fields and should be available in filters, columns, export, import, copy of cases, etc.

Steps to Create Custom Fields for Runs

...

Info
  • If the Run field is marked as mandatory, users will get the option to specify on which status the validation should be triggered- In Progress, Passed, Failed, and Blocked. Read the Accessing Run Custom Fields section to know how to access the custom fields.

  • The “Not Run” type of statuses status cannot be used for triggering validations.

...

The Custom fields will also appear on the right panels of all entities- Case, Set and Cycle. The image below is shown for Cycle. 

...

...

Anchor
Run
Run
Accessing Run Custom Fields

The custom fields defined for Runs are only available on the Execution tab within the Cycle Details page. Users can edit the custom fields by clicking on the Pencil icon next to the Custom Fields heading. 

...

assignee

assignee(s)

assignees

automation key

automation owner

automation status

automation-key

automation-owner

automation-status

automationkey

automationowner

automationstatus

component

created

data

description

end date

end-date

enddate

estimated effort

estimated effort(in mins)

estimated-effort

estimatedeffort

expected result

expected-result

expectedresult

folder

jira tasks

jira-tasks

jiratasks

key

objective

owner

pre conditions

pre-conditions

preconditions

priority

release

requirements

s.no.

start date

start-date

startdate

status

steps

tags

test count

test-count

testcount

title

type

updated

For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.