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

Comment and continue to the next Today item #429

New Issue
Closed
opened 2026-08-09 21:49:10 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 21:49:10 +00:00
Owner
Copy Link

User problem

On mobile, posting a status or handoff comment on the current Today issue or pull request leaves the operator in the same item. The existing separate “Done for Today & next” action adds an avoidable second step to the common non-terminal handoff flow.

Scope

Add a Comment & next action to the issue and pull-request composers. After an online post or durable offline admission, clear the draft, remove only the checkpointed current item from Today, and open the next item without closing or merging the Gitea item. Failed validation, API requests, or durable admission must preserve the draft and Today position. Hide the action when the sheet is not the active Today checkpoint.

Acceptance

  • Current Today issue and pull request post exactly once, leave the Gitea item open, complete it for Today, and open the next item.
  • Durable offline admission advances Today; failed admission does not.
  • Non-current sheets retain comment-only behavior.
  • Double submission cannot duplicate a comment or Today completion.
  • Mobile controls remain keyboard-visible with 44px touch targets.
  • Behavioral tests cover online, offline, failure, last-item, and non-current flows.

Evidence / non-duplication

Current comment handlers in frontend/dashboard.js only post/queue and clear drafts; they never call Today completion. Historical issues #421, #423, and #427 added Done-for-Today, review-and-next, and close-and-next respectively, but no historical issue or recent commit implements comment-and-next.

## User problem On mobile, posting a status or handoff comment on the current Today issue or pull request leaves the operator in the same item. The existing separate “Done for Today & next” action adds an avoidable second step to the common non-terminal handoff flow. ## Scope Add a **Comment & next** action to the issue and pull-request composers. After an online post or durable offline admission, clear the draft, remove only the checkpointed current item from Today, and open the next item without closing or merging the Gitea item. Failed validation, API requests, or durable admission must preserve the draft and Today position. Hide the action when the sheet is not the active Today checkpoint. ## Acceptance - Current Today issue and pull request post exactly once, leave the Gitea item open, complete it for Today, and open the next item. - Durable offline admission advances Today; failed admission does not. - Non-current sheets retain comment-only behavior. - Double submission cannot duplicate a comment or Today completion. - Mobile controls remain keyboard-visible with 44px touch targets. - Behavioral tests cover online, offline, failure, last-item, and non-current flows. ## Evidence / non-duplication Current comment handlers in `frontend/dashboard.js` only post/queue and clear drafts; they never call Today completion. Historical issues #421, #423, and #427 added Done-for-Today, review-and-next, and close-and-next respectively, but no historical issue or recent commit implements comment-and-next.
timmy self-assigned this 2026-08-09 21:49:10 +00:00
timmy closed this issue 2026-08-09 22:02:02 +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#429
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?