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

Reopen and resume closed issues from mobile Search #547

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

User problem

A mobile operator can close an assigned issue in Stackchain, but a premature close can only be recovered by leaving the app and rebuilding assignment and Today context manually. Closed Search results are currently read-only.

Vertical slice

From a closed issue Search preview, offer Reopen & resume. Capacity must be checked before mutation; the server must reopen and self-assign the issue convergently and confirm canonical state; the existing Today/session flow then starts the issue. Retries must be single-flight and truthful partial recovery must preserve the reopened issue in My Work.

Acceptance

  • Closed issues (not pull requests) advertise reopenability in preview and expose one mobile touch action.
  • A full Today blocks before any Gitea mutation.
  • Reopen confirms state=open and the authenticated user in assignees; incompatible ownership returns conflict.
  • Success adds exactly once to My Work/Today and starts it through the existing session flow.
  • Rapid taps share one request; failure leaves the preview retryable with accurate status.
  • Focused behavior tests and the full suite pass.

No historical issue title or recent commit implements issue reopening from Search (audited through origin/main 9c5b100 and releases through v0.1.0-rc.730).

## User problem A mobile operator can close an assigned issue in Stackchain, but a premature close can only be recovered by leaving the app and rebuilding assignment and Today context manually. Closed Search results are currently read-only. ## Vertical slice From a closed issue Search preview, offer **Reopen & resume**. Capacity must be checked before mutation; the server must reopen and self-assign the issue convergently and confirm canonical state; the existing Today/session flow then starts the issue. Retries must be single-flight and truthful partial recovery must preserve the reopened issue in My Work. ## Acceptance - Closed issues (not pull requests) advertise reopenability in preview and expose one mobile touch action. - A full Today blocks before any Gitea mutation. - Reopen confirms `state=open` and the authenticated user in assignees; incompatible ownership returns conflict. - Success adds exactly once to My Work/Today and starts it through the existing session flow. - Rapid taps share one request; failure leaves the preview retryable with accurate status. - Focused behavior tests and the full suite pass. No historical issue title or recent commit implements issue reopening from Search (audited through origin/main 9c5b100 and releases through v0.1.0-rc.730).
timmy self-assigned this 2026-08-11 06:21:00 +00:00
timmy closed this issue 2026-08-11 06:39:24 +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#547
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?