Overview
The customer wants system logs to retain meaningful user attribution even after a user has been deleted. Today, some completed records such as bills continue to display the deleted user’s name, while system logs replace that identity with a generic “deleted user” label. This creates an inconsistent experience and removes valuable historical context from audit trails. The requested improvement is for logs to preserve the original user identity while still clearly indicating that the user is no longer active.
Current Limitations
• System logs replace deleted users with a generic “deleted user” label.
• Other historical records, such as completed bills, may still retain the original user’s name.
• This inconsistency makes audit history harder to interpret.
• Important context about who performed an action is lost once a user is deleted.
• Support and customer teams have reduced confidence in logs as a reliable source of record.
General Example
A technician or administrator completes an action that is later recorded in the system log. If that user is subsequently deleted, the related log entry no longer shows who performed the action and instead displays “deleted user.” Meanwhile, other parts of the platform may still show the original name for completed records. This creates confusion when customers try to validate who made a change and when.
Requested Enhancements
- Preserve the original display name of a user in system logs after that user is deleted.
- Visually indicate deleted status without removing identity, such as showing the retained name with strikethrough formatting or a deleted badge/state indicator.
- Apply this behavior consistently across logs and historical records so user attribution is handled the same way throughout the platform.
- Ensure retained deleted-user attribution remains visible anywhere auditability or historical traceability is important.
Business Value
• Improves audit clarity by preserving who performed historical actions.
• Reduces confusion caused by inconsistent deleted-user handling across the system.
• Increases trust in logs as a source of truth for operational history.
• Helps support, administrators, and customers investigate past actions more efficiently.
• Maintains historical context while still signaling that the user is no longer active
