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

Assign available work and start it from Find #411

New Issue
Closed
opened 2026-08-09 16:11:15 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 16:11:15 +00:00
Member
Copy Link

Product gap

Find Work lets a mobile operator claim an issue, but beginning that work still requires leaving Find, reopening planning, finding the claimed issue, adding and saving it to Today, then starting the Today session. Existing create-and-start and checkpointed Today-session primitives already prove the end-to-end path for newly captured issues; Find does not connect to them.

Scope

Add an Assign & start action to available-work results. Capacity is checked before mutation. After one confirmed assignment, add the issue to Today, persist/sync it, warm offline data when enabled, begin a checkpointed Today session at that issue, and open its details. Keep existing Assign to me behavior unchanged.

Acceptance

  • Repeated taps produce exactly one assignment mutation.
  • A full Today plan blocks before assignment with a useful capacity message.
  • Assignment failure changes neither Today nor the active session and remains retryable.
  • Confirmed assignment adds/syncs the issue, starts a resumable Today session, and opens detail.
  • A post-assignment local-start failure truthfully reports assignment succeeded and opens the issue for recovery.
  • Paired actions remain usable at phone widths with 44px minimum touch targets.

Non-duplication evidence

All 208 historical issue titles and the latest 20 commits were checked. #175/#179 cover discover/preview/claim, #279/#385 cover Today planning/session, and #387/#389 cover Create & start for newly created issues. None connects Find Work assignment directly to Today start.

## Product gap Find Work lets a mobile operator claim an issue, but beginning that work still requires leaving Find, reopening planning, finding the claimed issue, adding and saving it to Today, then starting the Today session. Existing `create-and-start` and checkpointed Today-session primitives already prove the end-to-end path for newly captured issues; Find does not connect to them. ## Scope Add an **Assign & start** action to available-work results. Capacity is checked before mutation. After one confirmed assignment, add the issue to Today, persist/sync it, warm offline data when enabled, begin a checkpointed Today session at that issue, and open its details. Keep existing **Assign to me** behavior unchanged. ## Acceptance - Repeated taps produce exactly one assignment mutation. - A full Today plan blocks before assignment with a useful capacity message. - Assignment failure changes neither Today nor the active session and remains retryable. - Confirmed assignment adds/syncs the issue, starts a resumable Today session, and opens detail. - A post-assignment local-start failure truthfully reports assignment succeeded and opens the issue for recovery. - Paired actions remain usable at phone widths with 44px minimum touch targets. ## Non-duplication evidence All 208 historical issue titles and the latest 20 commits were checked. #175/#179 cover discover/preview/claim, #279/#385 cover Today planning/session, and #387/#389 cover Create & start for newly created issues. None connects Find Work assignment directly to Today start.
timmy was assigned by rockachopa 2026-08-09 16:21:15 +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#411
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?