Custom Fields

Custom fields allow to smooth out the information flow in ATM. Dive into details below.

We have introduced multiple custom fields in order for the app to be fully functional. These fields allow us to ensure the highest level of efficiency in testers' workflow and a smooth details flow, which prevents a disorganized testing process.

The listed custom fields are locked fields - they can only be added to selected screens. Locked fields are a part of the app and cannot be deleted from Jira. Users can fill them in, however they cannot change the custom fields names

Custom field	Where?	Meaning
ATM Environment	Test Executions & Test Case Executions	Collects environments. Admins can define them on the Environments page.
ATM Test Cases	Test Plans and Test Executions items	Collects issues that are defined as Test Cases.
ATM Test Plans	Test Cases item	Collects issues that are defined as Test Plans.
ATM Test Type	Test Cases item	Defines the nature of the Test Case. For now, this field is set to Manual for all Test Cases
ATM TE Status	Test Execution item	Shows the status of Test Execution. For now, the statuses are predefined.
ATM TE Progress	Test Execution item	Shows the progress based on Test Case Executions.

Disclaimer: ATM Test Plans and ATM Test Cases fields can only be edited in the Create work item dialog window. On the work item view they are read-only fields - the values showed in them are taken based on the actions from the Test Management panel. Additionally, the ATM Test Type field is read-only.

Search in JQL

The use of custom fields throughout the app allows the users to quickly retrieve specified information with a use of advanced JQL search. Two examples are portrayed below - more details regarding using JQL in search with app custom fields can be found here.

• Find testing items that have been assigned to staging environment

Test Environment = staging

• Search for Test Executions with status 'Fail'

TE Status = fail