Triage and verify issues

Step by step

1. Raise the issue Developer

   Developer or QA Engineer records the problem against the correct project, names the owner and supplies severity. Use the reporter's note to explain the observed result and its effect on the scheduled work.

   • Establish the problem, owner and severity
   • Updates Issues, Projects, Team members

2. Run guarded triage Developer

   When the existing issue is Open, the triage workflow checks that state and the presence of severity. Eligible work moves to Triaged and receives an operation receipt. A failed check records the failed attempt instead.

   • Record Triaged or a failed attempt
   • Updates Issues, Operation receipts

3. Work the resolution Developer

   The issue owner investigates the problem and keeps its state current as work proceeds. Project Manager follows any related task block and adjusts the working plan when the dependency remains unresolved.

   • Maintain investigation and blocking context
   • Updates Issues, Tasks

4. Present the fix Developer

   Developer records Fixed when the change is ready for verification and retains supporting files or links against the intended issue. Keep the issue visible until the actual outcome has been checked.

   • Retain Fixed work and supporting evidence
   • Updates Issues, Record attachments

5. Verify the result QA Engineer

   QA Engineer inspects the evidence and tests the relevant result before recording Verified. Project Manager confirms the remaining delivery impact before closing the issue and considering the affected work complete.

   • Record the verified outcome
   • Updates Issues, Record attachments, Tasks

Developer

, QA Engineer, Project Manager and Delivery Lead.