Report retention backlog without listing customer file names
The only retention report exports every filename to a general analytics dashboard.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Observability · Data minimization
Estimated field mix
- Privacy engineering60%
- Site reliability40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional support service keeps uploaded diagnostic files indefinitely. The exercise policy expires attachments 30 days after case closure, while a separately authorized investigation hold pauses removal. These are invented product rules, not legal advice or compliance certification.
Setup prerequisites
- Create synthetic cases, attachment metadata and a fake object store with controllable failures.
- Use an injected UTC clock and an authorized operator fixture; no real support uploads are needed.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- RRETENTION-101 · Calculate attachment expiry from the case closure instant
- RRETENTION-102 · Inventory every storage location used by one support attachment
- RRETENTION-103 · Require scoped authority to place an attachment on investigation hold
- RRETENTION-104 · Preview the attachment purge set with stable decision reasons
- RRETENTION-105 · Recheck holds when a queued attachment purge begins
- RRETENTION-106 · Retry partial attachment removal without forgetting derived copies
Acceptance criteria
- Expose aggregate eligible, held, failed and completed counts plus oldest eligible age.
- Keep filenames, object keys and case content out of generic metrics.
- Provide authorized drilldown through the scoped operational view instead of metric labels.
Implementation constraints
- Use bounded outcome categories and distinguish zero eligible records from unavailable measurements.
Verification to include
- Reconcile aggregate counts with a synthetic fixture containing each outcome.
- Insert sensitive-looking filenames and verify no value reaches the metric payload.
Deliverables
- Retention metrics and sanitized payload tests
Rollout and recovery
Run aggregate reporting beside the restricted preview; remove the old filename-based dashboard after validation.
Value of the work
For the engineer: Practice temporal policy, deletion races, exception authority and truthful recovery reporting.
For the team: Develop inspectable retention behavior that a company can review against its own approved data policy.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.