Page Comparison

...

Jira workflow

1. At the beginning of the week, the Product Owner will add a new Testing Feedback sub-task (manually or through import). Testing feedback sub-tasks are then assigned to the individual testers.

2. After testers review the test cases and have resolved any questions, transition the Testing Feedback issue to Mark Ready for Review from the status menu andit will move the issue into the working Backlog.

3. When testing begins, the tester will select Start Testing on the respective Testing Feedback issue, which sets status as In Progress. When appropriate, please feel free to create and attached screen recordings or screen captures and attach to the Testing Feedback issue.

4. If a test case is being skipped, select Close the issue from the status drop with a resolution of “Won't Do”.

5. If the behavior is satisfactory, transition the status to Closed, with a resolution of Complete.

6. If there is unexpected behavior, select Kick Back for PM Review.

7. When it's in PM Review the PO can triage and either move to Closed in the case where the report is considered expected behavior or, Park for Development which transitions to a status On Hold pending completion of a related Bug or Story issue (artifact to describe the undesired behavior). This is a separate issue created in Jira (K-Int Team) or Rally (Dreamliner Team) or wherever as appropriate for the team doing the work. 

8. The PO will add a link in the External Issue field if the issue resides outside of Jira. Or (if in DCB Jira) link the new Bug/Story issue to the Test Case or Testing Feedback issue with the `User Feedback` link (ie, [Bug/Story] "reported by User Feedback Issue" [Testing Issue])

9. When the prior step is complete, the PO and the testers re-test against the original testing feedback issue and transition to Return for Review which returns it to the Backlog.

10. The PO should/may need to move it to a new tighter scoped Test Case issue if it's a new test cycle.

...