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

Require a Today estimate before Create & start #849

New Issue
Closed
opened 2026-08-14 20:19:50 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 20:19:50 +00:00
Owner
Copy Link

Problem

Mobile Create & start only checks the five-item Today limit. It can immediately start unestimated work even when the configured Today minute budget is already exhausted, bypassing the capacity model delivered in #459 and related batch-planning flows. No historical issue title or recent commit connects capture-time estimation to Create & start.

Vertical slice

Require a 5–1440 minute estimate for Create & start, expose current remaining Today capacity beside the control, preserve the estimate through durable/offline issue delivery, render it in the final filing review, and persist/sync it into Today before starting the work session. Ordinary Create & assign remains unchanged.

Acceptance tests

  • Create & start reveals and requires a touch-sized 5–1440 minute estimate; invalid values focus the field and do not open review.
  • The filing review shows the estimate and projected Today capacity.
  • The completion intent retains the estimate through outbox/background delivery.
  • After issue creation, Today stores and syncs the estimate before starting. If local planning persistence or sync admission fails, the issue is created but no session starts.
  • Existing Create & assign and legacy Today plans continue to work.
  • Focused tests and the full suite pass.
## Problem Mobile **Create & start** only checks the five-item Today limit. It can immediately start unestimated work even when the configured Today minute budget is already exhausted, bypassing the capacity model delivered in #459 and related batch-planning flows. No historical issue title or recent commit connects capture-time estimation to Create & start. ## Vertical slice Require a 5–1440 minute estimate for Create & start, expose current remaining Today capacity beside the control, preserve the estimate through durable/offline issue delivery, render it in the final filing review, and persist/sync it into Today before starting the work session. Ordinary Create & assign remains unchanged. ## Acceptance tests - Create & start reveals and requires a touch-sized 5–1440 minute estimate; invalid values focus the field and do not open review. - The filing review shows the estimate and projected Today capacity. - The completion intent retains the estimate through outbox/background delivery. - After issue creation, Today stores and syncs the estimate before starting. If local planning persistence or sync admission fails, the issue is created but no session starts. - Existing Create & assign and legacy Today plans continue to work. - Focused tests and the full suite pass.
timmy self-assigned this 2026-08-14 20:19:50 +00:00
timmy closed this issue 2026-08-14 20:44:46 +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#849
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?