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

Plan multiple My Work items from mobile queues #661

New Issue
Closed
opened 2026-08-12 15:55:40 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 15:55:40 +00:00
Owner
Copy Link

Problem

Mobile operators can batch-select only unread Updates. Issues, pull requests, and reviews still require opening each card’s collapsed planning disclosure and applying Today/Later one at a time.

Slice

Add queue-independent selection for eligible My Work cards and one sticky, phone-safe batch planner with Add to Today, Later today, Tomorrow, and Cancel. Today admission must be atomic against the five-item cap; Later must persist one wake time atomically. Keep updates unread and do not mutate Gitea records.

Acceptance

  • Select eligible issue, pull, review, and update cards from All, Attention, Issues, PRs, Reviews, and Updates.
  • Batch Today preserves visible order, ignores existing Today entries, and commits none if capacity or storage fails.
  • Batch Later applies one wake time atomically and leaves updates unread.
  • Failure retains selection; success clears it and keeps the active queue route.
  • At phone widths, selectors/actions are at least 44px and sticky actions sit above the mobile dock/safe area.
  • Existing update mark-read workflow remains available in Updates.
  • Focused and full suites pass.

Evidence / non-duplication

Current origin/main limits selection at frontend/dashboard.js:2341 to the Updates filter. Historical #545 and #659/#660 cover selected-update acknowledgement/defer only; #393/#394 cover per-card planning; #385/#386 and #633-#636 cover Today planning. No historical issue/PR or recent commit provides cross-kind queue selection with atomic batch Today admission.

## Problem Mobile operators can batch-select only unread Updates. Issues, pull requests, and reviews still require opening each card’s collapsed planning disclosure and applying Today/Later one at a time. ## Slice Add queue-independent selection for eligible My Work cards and one sticky, phone-safe batch planner with Add to Today, Later today, Tomorrow, and Cancel. Today admission must be atomic against the five-item cap; Later must persist one wake time atomically. Keep updates unread and do not mutate Gitea records. ## Acceptance - Select eligible issue, pull, review, and update cards from All, Attention, Issues, PRs, Reviews, and Updates. - Batch Today preserves visible order, ignores existing Today entries, and commits none if capacity or storage fails. - Batch Later applies one wake time atomically and leaves updates unread. - Failure retains selection; success clears it and keeps the active queue route. - At phone widths, selectors/actions are at least 44px and sticky actions sit above the mobile dock/safe area. - Existing update mark-read workflow remains available in Updates. - Focused and full suites pass. ## Evidence / non-duplication Current `origin/main` limits selection at `frontend/dashboard.js:2341` to the Updates filter. Historical #545 and #659/#660 cover selected-update acknowledgement/defer only; #393/#394 cover per-card planning; #385/#386 and #633-#636 cover Today planning. No historical issue/PR or recent commit provides cross-kind queue selection with atomic batch Today admission.
timmy self-assigned this 2026-08-12 15:55:40 +00:00
timmy closed this issue 2026-08-12 16:05:44 +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#661
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?