Jira Workflows

Dedicating a specified workflow for each testing element can help teams stay on track and don't get lost in the lifecycle of every item, even if the project board is filled to the maximum. Workflows provide crucial information regarding the progress of every testing phase and help maintain transparency.

In ATM, the testing elements, such as Requirements, Test Cases, Test Executions, etc. are native work items - which allows users to map each element with a Jira workflow easily.

Workflows listed below are just suggestions. As Jira is a customizable tool, the following examples can be further tailored to the team's strategy, ensuring a perfect alignment. Users can also find a short description of every stage for each of the testing elements.

Requirements

• New

  • The requirement has just been created and hasn’t been reviewed yet; this is the initial state after creation.

• Under Review

  • The item is actively being reviewed; this might involve stakeholders checking completeness, clarity, feasibility, and alignment with the project goals.

• Accepted

  • The requirement has passed review and is formally accepted as valid; it’s now considered ready for implementation or testing.

• Rejected

  • The element has been reviewed and deemed invalid, incomplete, or unnecessary.

• Archived

  • The finalized stage; the requirement is either implemented, tested, or officially retired; no further action is typically expected.

Test Cases/ Test Plans

• New

  • Test Case/Test Plan has been created but not yet validated. It might still need review for correctness, completeness, and alignment with requirements.

• Under Review

  • Test Case/Test Plan is being reviewed for quality, coverage, feasibility, and compliance with standards (or schedule in case of Test Plans).

• Rejected

  • The items were reviewed and determined to be invalid or unnecessary, or in need of major re-work.

• Approved

  • Test Case/ Test Plan passed review and is ready for execution in the test cycle.

• Archived

  • Test Case has been executed and finalized (results are logged, no more changes are expected).

  • Test Plan is finalized after execution of all associated test cases.

Test Executions

• Open

  • The Test Execution cycle has been created but not started yet; here, Test Cases should be linked and the environment should be ready.

• In Progress

  • Test Execution is currently happening; testers are running test cases, logging results (pass/fail), and reporting Defects.

• Closed

  • Test Execution is completed; all test cases in the cycle are executed, and results are finalized.

For Test Executions, ATM offers custom field ATM TE Status so that the users can easily follow the progression of tests. The statuses offered are more extensive than the ones presented in the workflow above. Users can decide to create more comprehensive workflow that matches the statuses of the custom field.

Statuses in ATM TE Status field:

• To Do

• In Progress

• Blocked

• Pass

• Fail