stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Complete review requests without leaving mobile Updates triage #775

New Issue
Closed
opened 2026-08-13 21:50:21 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 21:50:21 +00:00
Owner
Copy Link

User problem

Mobile Updates correctly prioritizes review-request notifications, but its decision bar only offers Keep unread, Mark read, Reply, and More. Operators must leave triage and rediscover the pull request in another queue before using the existing in-app review workspace.

Vertical slice

  • Show a thumb-reachable Review now action only for review-request pull updates.
  • Open the existing review workspace for the same pull while preserving the current unread notification and triage checkpoint.
  • Closing review returns to the same update without acknowledging it.
  • After an online review succeeds, or an offline review is durably queued, durably acknowledge the source notification and advance exactly once to the next update.
  • Submission/read-admission failure preserves the draft and current unread update.

Acceptance tests

  • Eligibility rejects issue/non-review updates and accepts review-request pulls with canonical repository/number metadata.
  • Handoff preserves the current notification through cancel/back.
  • Successful review precedes read acknowledgement and advances once only after both succeed.
  • Failed acknowledgement does not advance or silently remove the update.
  • Mobile action remains at least 44px and the rendered dashboard exposes the integrated flow.

Evidence: current origin/main prioritizes Review requested (frontend/my-work.js) but frontend/index.html has no direct review action; the review workspace already exists in frontend/dashboard.js. Historical audit of 390 issue records found no equivalent title/behavior; #765 only reviews kept-unread triage outcomes.

## User problem Mobile Updates correctly prioritizes review-request notifications, but its decision bar only offers Keep unread, Mark read, Reply, and More. Operators must leave triage and rediscover the pull request in another queue before using the existing in-app review workspace. ## Vertical slice - Show a thumb-reachable **Review now** action only for review-request pull updates. - Open the existing review workspace for the same pull while preserving the current unread notification and triage checkpoint. - Closing review returns to the same update without acknowledging it. - After an online review succeeds, or an offline review is durably queued, durably acknowledge the source notification and advance exactly once to the next update. - Submission/read-admission failure preserves the draft and current unread update. ## Acceptance tests - Eligibility rejects issue/non-review updates and accepts review-request pulls with canonical repository/number metadata. - Handoff preserves the current notification through cancel/back. - Successful review precedes read acknowledgement and advances once only after both succeed. - Failed acknowledgement does not advance or silently remove the update. - Mobile action remains at least 44px and the rendered dashboard exposes the integrated flow. Evidence: current `origin/main` prioritizes `Review requested` (`frontend/my-work.js`) but `frontend/index.html` has no direct review action; the review workspace already exists in `frontend/dashboard.js`. Historical audit of 390 issue records found no equivalent title/behavior; #765 only reviews kept-unread triage outcomes.
timmy self-assigned this 2026-08-13 21:50:21 +00:00
timmy closed this issue 2026-08-13 22:01:55 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
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: stackchain/stackchain-dashboard#775
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?