Give feedback on stories and track HOL responses
Backend work · Implementation on hold · Planned work
Backend implementation on hold. Planned backend work. No connected capability or completed implementation is recorded.
Story/Brief feedback submission and HOL triage/response. Uses existing stable story/section identities; no automatic edits to canonical backlog status, public approval badge or weekly record. Voting, attachments, notifications, full project-management tooling and a50-user pilot are outside this first story and need separate decisions.
Implementation status is separate from stakeholder approval and publication.
Goal
As an approved HOL reviewer, I want to submit feedback on a specific story or Brief section and see its review status so the team can understand, prioritize and respond to my input.
Verification when backend work is authorized
- Agree reviewer/triage permissions, visibility, status labels and record-retention rules.
- Implement and test submission plus the HOL triage/response workflow with synthetic records.
- Verify persistence, stable target links and denied access before requesting connection for real HOL feedback.
Backend requirements
- Define reviewer eligibility and who can read, submit and triage feedback before implementation. A member login or demo role selection alone does not grant stakeholder-review authority.
- Attach each submission to a stable story ID or section key and capture author, timestamp, content and status. Preserve the target context for later review.
- Provide a clear submission result and persist feedback across sessions. A submission must not silently mark a feature reviewed, approved or Done.
- Provide HOL-authorized triage with a recorded response and agreed status changes; define the minimum status list, visibility and change-history requirements.
- Test permitted submission/read/triage and denied anonymous, uninvited and unauthorized requests, including database enforcement and attempts against another target/user.
- Keep actual stakeholder feedback in HOL-owned storage, use synthetic records in dev/Andy staging and resolve backup/retention before inviting real reviewers.