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

Claim and start an unowned issue from mobile Filed #893

New Issue
Closed
opened 2026-08-15 12:51:13 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 12:51:13 +00:00
Owner
Copy Link

Problem

Mobile capture intentionally allows filing with no owner, but an authored unassigned issue becomes read-only in Filed. The author must leave the known filing receipt and rediscover the issue through Search/Find Work before taking ownership.

Slice

In the Filed issue sheet, expose Queue Today and Claim & start only after canonical detail confirms the authored issue is open and has no assignees. Reuse the existing capacity-gated, single-flight claim/start flow and reconcile the confirmed issue into My Work. Assigned-to-others, closed, completed, and non-Filed issues remain unchanged.

Acceptance

  • Canonically open, authored Filed issue with zero assignees exposes both actions on mobile.
  • Today capacity is checked before the claim request.
  • Repeated taps share one claim; confirmed assignment queues or starts exactly once.
  • Claim races keep the Filed item visible with truthful retry guidance.
  • Successful claim reconciles canonical owned work and exits the read-only Filed state.
  • Actions are thumb-safe at 320px/390px with no horizontal overflow.
  • Behavioral focused tests and full suite pass.

Audit evidence: frontend/my-work.js, frontend/issue-sheet.js, frontend/dashboard.js, and the existing /claim endpoint show the missing Filed-to-owned transition. Historical issue/PR title review found creation (#855), Filed follow-up (#870-#887), and claim/start from Find/Search (#175/#413), but no claim/start directly from Filed.

## Problem Mobile capture intentionally allows filing with no owner, but an authored unassigned issue becomes read-only in Filed. The author must leave the known filing receipt and rediscover the issue through Search/Find Work before taking ownership. ## Slice In the Filed issue sheet, expose **Queue Today** and **Claim & start** only after canonical detail confirms the authored issue is open and has no assignees. Reuse the existing capacity-gated, single-flight claim/start flow and reconcile the confirmed issue into My Work. Assigned-to-others, closed, completed, and non-Filed issues remain unchanged. ## Acceptance - Canonically open, authored Filed issue with zero assignees exposes both actions on mobile. - Today capacity is checked before the claim request. - Repeated taps share one claim; confirmed assignment queues or starts exactly once. - Claim races keep the Filed item visible with truthful retry guidance. - Successful claim reconciles canonical owned work and exits the read-only Filed state. - Actions are thumb-safe at 320px/390px with no horizontal overflow. - Behavioral focused tests and full suite pass. Audit evidence: `frontend/my-work.js`, `frontend/issue-sheet.js`, `frontend/dashboard.js`, and the existing `/claim` endpoint show the missing Filed-to-owned transition. Historical issue/PR title review found creation (#855), Filed follow-up (#870-#887), and claim/start from Find/Search (#175/#413), but no claim/start directly from Filed.
timmy self-assigned this 2026-08-15 12:51:13 +00:00
timmy closed this issue 2026-08-15 13:03:52 +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#893
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?