Capture the reported behavior and use the severity and state checks to establish a triaged defect.
QA Engineer or Developer records the summary and project, with the reporter notes explaining how to repeat the behavior. Keep the issue key available for later task cross-references. Identify the reporter and corrective owner where known, and start the report as Open.
QA Engineer chooses Critical, High, Medium or Low using the team's agreed definitions. Check that the notes explain the impact and expected result. Severity describes the defect; the Project Manager will separately decide the priority of corrective work.
The Defect Triage workflow processes the existing report when it is Open and severity is present. It moves the defect to Triaged and records an operation receipt. This is a state and completeness check, with no separate human approval gate.
QA Engineer reads the receipt and source report. Missing severity or a report no longer Open causes a failed attempt. Correct the actual cause before retrying, and retain the earlier receipt so the team can explain what happened.
QA Engineer confirms the defect owner. Project Manager selects the work package, creates the corrective task and assigns its Developer. Include the issue key in the task description so the Developer can find the report and its reproduction context.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.