ATM in Jira
This page is for Jira administrators. It lists what Appsvio Test Management (ATM) adds to Jira: work types, custom fields, screens, and workflows. It also shows what you can customize.
What ATM adds to Jira
ATM adds its testing objects to Jira when you create the sample project. That’s why we recommend that you always create the sample project when you start testing. See Quick Start.
Work types
When you create the sample project, ATM adds these testing objects, unless objects with the same names already exist:
- Test Case, as a Jira work type
- Test Plan, as a Jira work type
- Test Campaign, as a Jira work type
- Test Execution, as a Jira work type
- Test Case Execution, as ATM’s own object, not a Jira work item
Requirements and defects usually use work types that already exist in your Jira, for example Epic, Story, and Bug.
We recommend naming each work type after its testing object, for example Test Plan. In a Testing Project, you choose the space and the work type for each testing object. See Testing Elements and Testing objects & Relations.
Custom fields
ATM adds eight custom fields to Jira.
| Field | Work items | What it does |
|---|---|---|
| ATM Test Cases | Test Plan, Test Execution | Lists the linked Test Cases. |
| ATM Test Plans | Test Execution, Test Campaign | Lists the linked Test Plans. |
| ATM Repository | Test Case | Holds the folder of the Test Case in the Test Repository tree. |
| ATM Preconditions | Test Case | Holds the preconditions as formatted text. |
| ATM Test Type | Test Case | Shows the test type. The field is read-only and is always Manual for now. |
| ATM Environments | Test Execution, defect | Holds the selected test environments. |
| ATM TE Status | Test Execution | Holds the status of the Test Execution from a predefined list. It requires an active license. |
| ATM TE Progress | Test Execution | Shows the percentage of Test Case Executions in a final status. See how progress is calculated. |
You can add the ATM Environments field to the screen of your defects. Then you can search defects by environment. See Defects.
Screens and workflows
When you create the sample project, ATM also does the following:
- It adds the custom fields to the right screens for each type of testing object.
- It creates its own workflows for its work types.
If you configure a space for ATM by hand, check all these settings yourself: work types, custom fields on screens, and workflows. You can use the sample project as a reference.
When you save the configuration of a Testing Project, ATM adds its fields to the view of each mapped testing object. See Testing Elements.
What you can customize
Workflows
Test Cases, Test Plans, Test Campaigns, and Test Executions are Jira work items, so they use Jira workflows. For example, you can set up an acceptance workflow for Test Cases or an approval workflow for Test Plans.
Your own custom fields
You can extend testing objects with any information you need, stored in your own custom fields. To group and search Test Cases by such fields, see Using Jira Fields.
Company-managed and team-managed spaces
ATM supports both company-managed and team-managed spaces. The sample project is company-managed.