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

Make mobile Agenda discover every assigned deadline #703

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

Problem

Agenda is derived from only the currently loaded issue page. With more than 50 assigned issues, a deadline on page 2+ is absent from the Agenda count, fresh mobile launch choice, and rendered queue. Generic pagination is manual, so Agenda can imply no deadline work while older assigned deadlines remain undiscovered.

Vertical slice

When Agenda is active, sequentially and single-flight load the remaining issue pages through the existing bounded work-page endpoint. Render a truthful checking state until discovery completes, retain loaded cards on failure, and retry from the failed page. Other queues remain manually paginated.

Acceptance tests

  • Activating Agenda automatically loads issue pages until has_more=false and reveals a deadline from page 2.
  • Concurrent Agenda activation is single-flight.
  • A failed later page preserves loaded data and retry resumes at that page.
  • Agenda never shows a definitive empty state while discovery is incomplete.
  • Mobile controls/status remain phone-safe and other queues generate no extra requests.

No existing open/closed issue or recent commit implements pagination-complete Agenda discovery; #169 is generic manual pagination and #685/#693/#697/#701 cover Agenda derivation, routing, continuation, and launch selection only.

## Problem Agenda is derived from only the currently loaded issue page. With more than 50 assigned issues, a deadline on page 2+ is absent from the Agenda count, fresh mobile launch choice, and rendered queue. Generic pagination is manual, so Agenda can imply no deadline work while older assigned deadlines remain undiscovered. ## Vertical slice When Agenda is active, sequentially and single-flight load the remaining issue pages through the existing bounded work-page endpoint. Render a truthful checking state until discovery completes, retain loaded cards on failure, and retry from the failed page. Other queues remain manually paginated. ## Acceptance tests - Activating Agenda automatically loads issue pages until `has_more=false` and reveals a deadline from page 2. - Concurrent Agenda activation is single-flight. - A failed later page preserves loaded data and retry resumes at that page. - Agenda never shows a definitive empty state while discovery is incomplete. - Mobile controls/status remain phone-safe and other queues generate no extra requests. No existing open/closed issue or recent commit implements pagination-complete Agenda discovery; #169 is generic manual pagination and #685/#693/#697/#701 cover Agenda derivation, routing, continuation, and launch selection only.
timmy closed this issue 2026-08-13 03:27:34 +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#703
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?