Banner

Introduce a first-class Issue Audit Log that records and displays all meaningful changes to an issue (status, priority, severity, assignee, comments, etc.) via a dedicated modal launched from the Issues page.

Description

Sztab currently lacks visibility into how and when an issue evolved. This makes debugging, accountability, and collaboration harder, especially for long-lived or frequently updated issues.

This task introduces an Issue Audit Log, covering both backend persistence and frontend visualization.

UI Scope

• Add an Audit action to each issue row on IssuesPage
• Clicking Audit opens a read-only IssueAuditModal
• The modal displays a chronological timeline of changes for the selected issue
• Each audit entry includes:
  • timestamp
  • actor (user)
  • action type (status change, field update, comment added, etc.)
  • before and after values, where applicable

The audit modal is parallel to Edit, not embedded within it.

Backend Scope

• Introduce an IssueAuditEntry entity persisted per issue
• Record audit entries on:
  • issue creation
  • updates to status, priority, or severity
  • assignee changes
  • comments added
• Expose a REST endpoint that returns a sorted list of audit entries for an issue

Explicit Non-Goals

• No diff highlighting or advanced visual comparison
• No pagination (assume reasonable audit sizes initially)
• No new permissions logic beyond existing issue visibility rules

Deliverables

Frontend

• IssueAuditModal.tsx
• issueAudit.ts API client
• IssuesPage.tsx wiring (Audit action alongside Edit)
• Read-only, clean timeline UI

Backend

• IssueAuditEntry JPA entity
• IssueAuditEntryRepository
• IssueAuditService and IssueAuditServiceImpl
• Controller endpoint under IssueController

Worklog & Estimate