Custom fields
ATM uses several custom fields to ensure full functionality, streamline testing workflows, and keep your testing process organized.
Caution
These custom fields are locked. This means they are a core part of the app and cannot be deleted or renamed in Jira. You can fill them in and add them to selected screens, but their core configuration remains locked.
| Custom field | Used in | Description |
|---|---|---|
| ATM Environments | Requirements, Test Cases, Test Plans, Test Executions, Test Case Executions, Defects | Stores the selected testing environments. Admins can configure these in the Testing Hub. |
| ATM Repository | Test Cases | Displays the location of the Test Case within the folder structure. |
| ATM Precondition | Test Cases, Test Case Executions | Defines the criteria that must be met before starting the test execution. |
| ATM Test Cases | Test Plans, Test Executions | Lists the associated Test Case issues. |
| ATM Test Type | Test Cases | Defines the nature of the test. Currently, this field is always set to Manual. |
| ATM Test Plans | Test Executions | Lists the associated Test Plan issues. |
| ATM TE Status | Test Executions | Displays the current status of the Test Execution (statuses are predefined). |
| ATM TE Progress | Test Executions | Displays the overall execution progress based on linked Test Case Executions. |
Important note
The ATM Test Plans and ATM Test Cases fields can only be edited during the creation process (in the Create issue dialog). On the issue view, they become read-only, and their values are managed directly via the Test Management panel. The ATM Test Type field is always read-only.
Search in JQL
Because ATM utilizes Jira custom fields, you can easily retrieve specific testing data using advanced JQL searches. You can find detailed instructions and examples on the dedicated JQL search page.