Separate defect repair from affected-customer results
Synthetic defect D-191 links three customer cases. A confirms the corrected export, B has not tested and C still fails under a different setting. The shared repair record is verified for its own test condition, but the customer recovery count is one of three. Keep B’s pending check and C’s remaining investigation visible. The list is the declared fixture set, not an assertion that no other customer is affected.
| Customer case | Current observation | Task state | Next action |
|---|---|---|---|
| A | Corrected export succeeds | Restored | Retain evidence |
| B | Not tested | Pending confirmation | Obtain task result |
| C | Different setting still fails | Unresolved | Investigate setting-specific case |
Update each linked outcome independently
- Read declared affected-customer set
- Collect individual task checks
- Record restored, pending or unresolved
- Report counts with that scope
A customer outside the listed set needs its own impact check; do not infer eligibility from the shared defect label.
What recovery fraction is evidenced in this three-case set?
Show the worked answer
1/3 customer cases, approximately 33.3%. This is a fixture subtotal; B is unknown and C remains unresolved.
Label recovery counts with the declared customer set. Expand the set when further affected cases are verified and keep unknown checks visible.