Skip to content

UX: Add business context (task/requirement) to diff viewer file tree #480

Description

@frankbria

Problem

DiffViewer and FileTreePanel on the Review page show changed files but don't indicate which task or PRD requirement caused each change. With 50+ changed files, reviewers lose business context.

Impact

Code review becomes purely technical — reviewers cannot assess correctness without knowing why each file was modified. Context switching to other tools breaks flow.

Recommendation

  1. Add 'changed by' metadata to each file in the diff (task title, requirement ID if available)
  2. Display task/requirement label in FileTreePanel next to each filename
  3. Add 'View Task →' link in diff header for the active file
  4. Group files by task in the file tree (collapsible)

Acceptance Criteria

  • Task name visible in file tree next to filename
  • Requirement ID shown in diff header when available
  • 'View Task' link navigates to task detail
  • File tree supports grouping by task
  • Works for multi-task diff sessions

Affected Components

web-ui/src/components/review/DiffViewer.tsx, web-ui/src/components/review/FileTreePanel.tsx

Metadata

Metadata

Assignees

No one assigned

    Labels

    phase-6.3Phase 6.3: UX/UI design improvements for user journey through Think→Build→Prove→Shippriority:mediumux

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions