Using Jira Fields
Because ATM Test Cases are standard Jira issues, you can take full advantage of native Jira fields to categorize and organize your tests. This method works perfectly alongside the ATM Repository and Test Plans, adding another dimension to your test organization.
Recommended Fields for Organization
Components
The native Jira Components field is excellent for categorizing tests by technical architecture (e.g., Database, API, UI). Components are managed by project administrators, ensuring a clean and standardized list of values.
Team
The native Team field is a fantastic way to assign and organize Test Cases based on the specific Agile team responsible for that area of the product (e.g., Checkout Team, Mobile App Team).
Custom Select Fields
You can create your own custom dropdown fields (Single or Multiple Choice) tailored to your testing process. For example, a custom field named Testing Phase (with options like Smoke, Sanity, Regression) to easily filter tests needed for different stages of the release cycle.
A Note on Labels
While you can use the native Jira Labels field to tag Test Cases, we do not recommend relying on it as a primary organization method.
Caution
Labels are global and unmanaged in Jira. Any user can create a new label at any time, which often leads to messy data, typos (e.g., frontend, Front-end, front_end), and difficulties in reporting and filtering.
Use Case Example (Combining Methods): Your organization methods can overlap to give you powerful filtering capabilities. For example, a Test Case might be physically located in the ATM Repository under
E-commerce / Checkout. However, it is also assigned the ComponentPayment Gatewayand has a custom field Testing Phase set toRegression. When building a Test Plan, you can use JQL to easily find: All regression tests for the payment gateway within the checkout module.