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

Plan upcoming deadlines from a mobile Agenda #685

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

Product gap

Future assigned issue deadlines are only low-priority card badges; mobile queues expose overdue/due-today Attention but no chronological view of what is due next. Operators must scan broad queues to plan upcoming commitments.

Vertical slice

Add an Agenda queue that groups assigned issues due Overdue, Today, Tomorrow, and Next 7 days; sorts deterministically by deadline; distinguishes items already in Today or deferred to Later; and opens the existing issue workflow from a phone-safe queue. Agenda must be available from the mobile queue switcher and from Queue & settings, preserve the existing offline snapshot behavior, and make no mutation merely by opening it.

Acceptance tests

  • Assigned issues due yesterday, today, tomorrow, and within seven days appear in the correct local-calendar group; later/no-date/unassigned items do not.
  • Items sort by due instant, repository, then issue number.
  • Agenda count and route appear in the mobile queue switcher and My Work filters.
  • Agenda cards expose deadline group labels and continue using the existing issue-detail action.
  • Deferred items remain out of active Agenda; Today items retain their existing Today planning state.
  • At phone widths the queue is one-column, has 44px controls, and does not horizontally overflow.
  • Focused tests and the full suite pass; opening Agenda causes no Today/Gitea mutation.

Non-duplication evidence

Checked 345 historical issues, 336 historical PRs, and recent origin/main history at 16b1d86. No Agenda/upcoming-deadline queue exists. Closest work is #273 (overdue/due-today Attention), #459/#633 (generic Today capacity planning), and #683 (cross-queue continuation); none provides a future-deadline planning queue.

## Product gap Future assigned issue deadlines are only low-priority card badges; mobile queues expose overdue/due-today Attention but no chronological view of what is due next. Operators must scan broad queues to plan upcoming commitments. ## Vertical slice Add an Agenda queue that groups assigned issues due Overdue, Today, Tomorrow, and Next 7 days; sorts deterministically by deadline; distinguishes items already in Today or deferred to Later; and opens the existing issue workflow from a phone-safe queue. Agenda must be available from the mobile queue switcher and from Queue & settings, preserve the existing offline snapshot behavior, and make no mutation merely by opening it. ## Acceptance tests - Assigned issues due yesterday, today, tomorrow, and within seven days appear in the correct local-calendar group; later/no-date/unassigned items do not. - Items sort by due instant, repository, then issue number. - Agenda count and route appear in the mobile queue switcher and My Work filters. - Agenda cards expose deadline group labels and continue using the existing issue-detail action. - Deferred items remain out of active Agenda; Today items retain their existing Today planning state. - At phone widths the queue is one-column, has 44px controls, and does not horizontally overflow. - Focused tests and the full suite pass; opening Agenda causes no Today/Gitea mutation. ## Non-duplication evidence Checked 345 historical issues, 336 historical PRs, and recent origin/main history at 16b1d86. No Agenda/upcoming-deadline queue exists. Closest work is #273 (overdue/due-today Attention), #459/#633 (generic Today capacity planning), and #683 (cross-queue continuation); none provides a future-deadline planning queue.
timmy closed this issue 2026-08-12 22:30:57 +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
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#685
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?