Assign the correction, hand it to QA and close only after the reported behavior has been independently checked.
Project Manager creates the corrective task within its work package, selects the assignee and sets priority. Include the issue key in the task description. Confirm that the task and work package belong to the intended project before discussing delivery dates or effort.
Developer starts the correction and updates task progress. Record a blocking reason if work cannot continue. Keep the defect's owner informed and retain the original reporter notes so the expected behavior stays clear during investigation.
Developer marks the defect Fixed when the correction is ready and moves the task into review. Supply the context QA needs to repeat the reported behavior and locate the supporting evidence. Fixed signals readiness for assessment.
QA Engineer repeats the reported conditions and decides whether the correction is acceptable. Move the defect to Verified only after a successful independent check. A failed retest remains unverified, with an explanation for the Developer. Record acceptance of the corrective task using its actual task reference and project.
QA Engineer checks that verification evidence is retained before closing the defect. Project Manager confirms the accepted task can become Done. The defect's verification and the task's completion must remain separately traceable.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.