Typical scenario to manage defect progression and status

1.Technician executes tests  and identifies a potential defect

2. Technician fills out the defect report, he/she assigns it to an Engineer for analysis and to fix it if needed

• Status = Assigned
• Severity should be set by technician

3. Engineer determines if defect is reproducible and  valid to be fixed,  and proposes version to fix

• Status = Ack
• Priority should be set by Engineer
• Target Date and Version can be updated if known
• Update the completion e.g. to 20%

4. When planned or available, Engineer does the fix to code, verify from his/her standpoint and requests for validation

• Status = Resolved
• Correction Type = Corrected (if he was able to reproduce and fix)
• Completion = 70% maximum 

5. Technician executes same tests and reports back to Engineer  that the defect is fixed

• Status = Closed
• Completion = 100% maximum

Alternative 

5' . Technician 

executes same tests and reports back to Engineer that the defect 

is

NOT fixed

• Status = assigned --> back to stage 2 
• Completion = 70% maximum

Note : the setting of completion is somewhat arbitrary and may relay on various aspects depending on companies policies. It really depnds how you want to use the completion in you project.