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

Reassign open delegated issues from mobile Filed #895

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

User problem

An issue author can file work to a teammate and later review, revise, withdraw, reply to, or claim unowned work from mobile Filed, but cannot redirect an open assigned issue when the delegate is unavailable or incorrect. They must leave Stackchain and use Gitea.

Scope

Add an author-only Change delegate flow for open, non-PR Filed issues. Load eligible repository assignees, show the current delegate, require an explicit old → new confirmation, and replace the assignee only if the issue is still open, authored by the current operator, and still has the reviewed assignee. Keep the item in Filed and update its visible owner after success.

Acceptance criteria

  • At 390×844, an assigned open Filed issue exposes a thumb-safe Change delegate action and clear old → new confirmation.
  • Successful reassignment refreshes the owner in place and keeps the issue in Filed.
  • Closed issues, pull requests, non-authors, same-recipient requests, and ineligible recipients are rejected.
  • A changed current assignee returns conflict instead of overwriting newer state.
  • Cancel and upstream failure perform no mutation; failure remains retryable.
  • Behavioral API/UI tests and the full suite pass.

Non-duplication evidence

Historical-title and recent-commit scans found no delegated reassignment flow. #281 hands off work assigned to the current operator, #843 chooses an owner only at filing time, and #893 claims only unassigned Filed work.

## User problem An issue author can file work to a teammate and later review, revise, withdraw, reply to, or claim unowned work from mobile Filed, but cannot redirect an open assigned issue when the delegate is unavailable or incorrect. They must leave Stackchain and use Gitea. ## Scope Add an author-only **Change delegate** flow for open, non-PR Filed issues. Load eligible repository assignees, show the current delegate, require an explicit old → new confirmation, and replace the assignee only if the issue is still open, authored by the current operator, and still has the reviewed assignee. Keep the item in Filed and update its visible owner after success. ## Acceptance criteria - At 390×844, an assigned open Filed issue exposes a thumb-safe Change delegate action and clear old → new confirmation. - Successful reassignment refreshes the owner in place and keeps the issue in Filed. - Closed issues, pull requests, non-authors, same-recipient requests, and ineligible recipients are rejected. - A changed current assignee returns conflict instead of overwriting newer state. - Cancel and upstream failure perform no mutation; failure remains retryable. - Behavioral API/UI tests and the full suite pass. ## Non-duplication evidence Historical-title and recent-commit scans found no delegated reassignment flow. #281 hands off work assigned to the current operator, #843 chooses an owner only at filing time, and #893 claims only unassigned Filed work.
timmy self-assigned this 2026-08-15 13:27:32 +00:00
timmy closed this issue 2026-08-15 13:50:02 +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#895
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?