feat(projects): show the project's own change history and edited marker (PMS-205) #113

Merged
longjacksonle merged 1 commit from feat/mapps-205-project-history into main 2026-06-11 04:39:54 +02:00

What

Implements PMS-205: the project detail page now shows the project's own change history (who/when + before/after content) and an "edited" marker on the Overview, matching what tasks already had.

SPA only - no backend change. The backend already records project edits (update_project writes before/after snapshots and projects is whitelisted by GET /audit-log/entity/{type}/{id}); the page just never surfaced them.

Changes

  • New project history resource fetching GET /api/v1/audit-log/entity/projects/{id}.
  • A Change History card on the project detail (sidebar) listing each edit: action + changed fields, actor resolved to a name, timestamp, and the per-field old → new content (reusing the PMS-204 formatting helpers).
  • An "Edited {when} by {who}" marker under the project Overview.
  • The project-edit modal restarts the history resource on save, so a fresh edit shows immediately.

Acceptance criteria

  • The project Overview shows an "edited" marker (who / when) after a project edit.
  • The project detail shows a Change History with the before/after content of each edit.

🤖 Generated with Claude Code

## What Implements PMS-205: the project detail page now shows the project's **own** change history (who/when + before/after content) and an "edited" marker on the Overview, matching what tasks already had. SPA only - no backend change. The backend already records project edits (`update_project` writes before/after snapshots and `projects` is whitelisted by `GET /audit-log/entity/{type}/{id}`); the page just never surfaced them. ## Changes - New project history resource fetching `GET /api/v1/audit-log/entity/projects/{id}`. - A **Change History** card on the project detail (sidebar) listing each edit: action + changed fields, actor resolved to a name, timestamp, and the per-field `old → new` content (reusing the PMS-204 formatting helpers). - An **"Edited {when} by {who}"** marker under the project Overview. - The project-edit modal restarts the history resource on save, so a fresh edit shows immediately. ## Acceptance criteria - [x] The project Overview shows an "edited" marker (who / when) after a project edit. - [x] The project detail shows a Change History with the before/after content of each edit. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(projects): show the project's own change history and edited marker (PMS-205)
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 49s
Create release / Create release from merged PR (pull_request) Has been skipped
4da1a9ae89
The project detail page let you edit the Overview and the backend already recorded each edit (entity_type "projects" is whitelisted by the history endpoint and update_project writes before/after snapshots), but the page never surfaced it. Add a project history resource (GET /audit-log/entity/projects/{id}), a Change History card on the project detail showing who/when plus the before/after content of each edit (reusing the PMS-204 helpers), and an "Edited {when} by {who}" marker on the Overview card. The project-edit modal now restarts the history resource on save so a fresh edit shows immediately. SPA only, no backend change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
longjacksonle deleted branch feat/mapps-205-project-history 2026-06-11 04:39:54 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
psa-systems/mokosh-apps!113
No description provided.