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

Replan overdue Agenda deadlines in one mobile sweep #707

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

Problem

Agenda surfaces overdue assigned issues, but rescheduling each one requires repeatedly opening an issue, expanding generic planning controls, saving, closing, and finding the next overdue item. This makes mobile deadline cleanup slow and error-prone.

Scope

Add a bounded Replan overdue flow to Agenda. It opens overdue issues in chronological order and supports Keep date & next, Tomorrow & next, and choosing a future date. Successful changes regroup Agenda before advancing; failures preserve the current item for retry; Cancel/Back returns to Agenda without mutation.

Acceptance criteria

  • Agenda shows the overdue count and starts with the earliest overdue issue.
  • Keep advances without a request; Tomorrow and a valid chosen future date use the existing confirmed due-date mutation.
  • Failed mutations do not advance or alter the local queue.
  • Controls are accessible and usable at 320px without horizontal overflow, with 44px touch targets.
  • Completing/canceling returns to #/my-work/agenda.
  • Behavioral tests cover ordering, success, failure, validation, and mobile markup/CSS.

Non-duplication evidence

Historical Agenda work (#685, #693, #697, #701, #703, #705 and linked PRs) added grouping, routing, continuation, discovery, launch, and dock visibility. None adds overdue deadline editing or a multi-item replanning flow. Current open issues #1-#5 and #11 are assigned to other humans and cover unrelated work. There are no open PRs.

## Problem Agenda surfaces overdue assigned issues, but rescheduling each one requires repeatedly opening an issue, expanding generic planning controls, saving, closing, and finding the next overdue item. This makes mobile deadline cleanup slow and error-prone. ## Scope Add a bounded **Replan overdue** flow to Agenda. It opens overdue issues in chronological order and supports Keep date & next, Tomorrow & next, and choosing a future date. Successful changes regroup Agenda before advancing; failures preserve the current item for retry; Cancel/Back returns to Agenda without mutation. ## Acceptance criteria - Agenda shows the overdue count and starts with the earliest overdue issue. - Keep advances without a request; Tomorrow and a valid chosen future date use the existing confirmed due-date mutation. - Failed mutations do not advance or alter the local queue. - Controls are accessible and usable at 320px without horizontal overflow, with 44px touch targets. - Completing/canceling returns to `#/my-work/agenda`. - Behavioral tests cover ordering, success, failure, validation, and mobile markup/CSS. ## Non-duplication evidence Historical Agenda work (#685, #693, #697, #701, #703, #705 and linked PRs) added grouping, routing, continuation, discovery, launch, and dock visibility. None adds overdue deadline editing or a multi-item replanning flow. Current open issues #1-#5 and #11 are assigned to other humans and cover unrelated work. There are no open PRs.
timmy self-assigned this 2026-08-13 04:20:01 +00:00
timmy closed this issue 2026-08-13 04:29:07 +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#707
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?