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

Watch assigned issues and pull requests from mobile detail #1309

New Issue
Closed
opened 2026-08-23 14:20:50 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-23 14:20:50 +00:00
Member
Copy Link

User problem

Operators reading an assigned issue or pull request in My Work must leave the detail, reopen Search, find the same item, and open its preview before they can add it to Following.

Vertical slice

Add a truthful Watch/Stop watching control to both assigned issue and pull-request detail sheets. Reuse the existing typed preview subscription endpoint so admission updates Gitea and Following atomically, refresh the Following queue/count after confirmation, prevent duplicate taps, and preserve truthful partial/failure outcomes. Watching must not change assignment or Today/Later planning.

Acceptance tests

  • Issue and pull detail controls load authoritative typed subscription state and show Watch issue / Watch pull request / Stop watching.
  • Mutation is single-flight, refreshes Following after confirmed sync, and never claims success for following_synced:false or network failure.
  • Controls remain at least 44px high with no horizontal overflow at 320x568 and 390x844.
  • Search watch and Following review behavior remain green.

Evidence / non-duplication

Current main exposes watching only in Search Preview (frontend/dashboard.js around renderSearchPreviewWatch) while issue and pull detail action rows omit it (frontend/index.html issue actions around 1182 and pull actions around 1720). Historical issue/PR title and recent commit audits show the #1293-#1308 Following series covers Search admission and review, but not admission from assigned detail. No open eligible issue covers this behavior.

## User problem Operators reading an assigned issue or pull request in My Work must leave the detail, reopen Search, find the same item, and open its preview before they can add it to Following. ## Vertical slice Add a truthful Watch/Stop watching control to both assigned issue and pull-request detail sheets. Reuse the existing typed preview subscription endpoint so admission updates Gitea and Following atomically, refresh the Following queue/count after confirmation, prevent duplicate taps, and preserve truthful partial/failure outcomes. Watching must not change assignment or Today/Later planning. ## Acceptance tests - Issue and pull detail controls load authoritative typed subscription state and show Watch issue / Watch pull request / Stop watching. - Mutation is single-flight, refreshes Following after confirmed sync, and never claims success for `following_synced:false` or network failure. - Controls remain at least 44px high with no horizontal overflow at 320x568 and 390x844. - Search watch and Following review behavior remain green. ## Evidence / non-duplication Current main exposes watching only in Search Preview (`frontend/dashboard.js` around `renderSearchPreviewWatch`) while issue and pull detail action rows omit it (`frontend/index.html` issue actions around 1182 and pull actions around 1720). Historical issue/PR title and recent commit audits show the #1293-#1308 Following series covers Search admission and review, but not admission from assigned detail. No open eligible issue covers this behavior.
timmy was assigned by rockachopa 2026-08-23 14:20:50 +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#1309
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?