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

Withdraw open delegated issues from mobile Filed #884

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

User problem

An issue author can file and follow a delegated issue from the mobile Filed queue, but cannot withdraw work that is obsolete, duplicated, or filed in error without leaving Stackchain.

Vertical slice

From My Work → Filed, an author opens an unassigned/delegated open issue, chooses Withdraw issue, confirms, and Stackchain closes the issue upstream. The result remains visible through the existing completed Filed review flow. Assigned work keeps its existing Close action.

Acceptance criteria

  • Open authored Filed issues expose a thumb-reachable Withdraw issue action while planning, assignment, edit, handoff, and defer controls remain unavailable.
  • Confirmation names the issue and explains that withdrawal closes the delegated request.
  • The close API accepts explicit access=filed, requires the authenticated operator to be the author, still requires CSRF and step-up authorization, and never calls Gitea for another author or a stale/closed item.
  • Success requires Gitea to confirm state: closed; repeated taps cannot duplicate the mutation.
  • On success the issue enters the existing completed Filed review flow; failures leave it visible with a retryable status.
  • Behavioral API and frontend tests cover authorization, stale state, request URL, visibility, confirmation, single-flight behavior, and queue transition.

Non-duplication evidence

All historical issue titles and recent commits were reviewed. #391 covers closing assigned Today work; #547 covers reopening Search results; #870–#882 cover Filed visibility, replies, completion review, synchronization, and history. No historical issue or recent commit implements author-initiated withdrawal from Filed.

## User problem An issue author can file and follow a delegated issue from the mobile Filed queue, but cannot withdraw work that is obsolete, duplicated, or filed in error without leaving Stackchain. ## Vertical slice From **My Work → Filed**, an author opens an unassigned/delegated open issue, chooses **Withdraw issue**, confirms, and Stackchain closes the issue upstream. The result remains visible through the existing completed Filed review flow. Assigned work keeps its existing Close action. ## Acceptance criteria - Open authored Filed issues expose a thumb-reachable **Withdraw issue** action while planning, assignment, edit, handoff, and defer controls remain unavailable. - Confirmation names the issue and explains that withdrawal closes the delegated request. - The close API accepts explicit `access=filed`, requires the authenticated operator to be the author, still requires CSRF and step-up authorization, and never calls Gitea for another author or a stale/closed item. - Success requires Gitea to confirm `state: closed`; repeated taps cannot duplicate the mutation. - On success the issue enters the existing completed Filed review flow; failures leave it visible with a retryable status. - Behavioral API and frontend tests cover authorization, stale state, request URL, visibility, confirmation, single-flight behavior, and queue transition. ## Non-duplication evidence All historical issue titles and recent commits were reviewed. #391 covers closing assigned Today work; #547 covers reopening Search results; #870–#882 cover Filed visibility, replies, completion review, synchronization, and history. No historical issue or recent commit implements author-initiated withdrawal from Filed.
timmy self-assigned this 2026-08-15 09:51:06 +00:00
timmy closed this issue 2026-08-15 10:07:43 +00:00
timmy reopened this issue 2026-08-15 10:10:21 +00:00
timmy closed this issue 2026-08-15 10:16:40 +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#884
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?