Help / Issues & remediation
Keep the corrective-action trail attached to the failure.
An issue should explain what failed, who owns the response, what corrective action was taken and how the result was verified.
Failed test→Issue→Corrective action→Retest→Close
Create the issue in context
When possible, create the issue from the failed test or system record. That preserves the project, site, system and test context needed by the person resolving the problem.

Record corrective action
Describe what was changed, replaced, configured or repaired. Use the issue status to make responsibility visible while the problem is still open.

Verify before closing
Resolution is not the same as verification. Where the issue originated from testing, retest the affected item and record the result before closing the issue.
When the system is ready
Acceptance should reflect both completed testing and any agreed exceptions that remain open.
Continue to Acceptance & handover →