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

Hand off assigned issues to teammates from mobile #281

New Issue
Closed
opened 2026-08-08 08:28:39 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-08 08:28:39 +00:00
Member
Copy Link

User problem

Mobile operators can release an assigned issue, but cannot transfer ownership to an eligible teammate. Release drops sole-assignee work into the unowned pool and breaks accountability.

Evidence

  • frontend/issue-sheet.js only exposes /release for assignment changes.
  • src/gitea_proxy.py::release_assigned_issue removes the current operator without selecting a successor.
  • Complete title review (143 issues, 134 PRs) found review-handoff work but no assigned-issue reassignment flow.

Acceptance

  • List eligible repository assignees, excluding the current operator and malformed records.
  • Transfer an open issue only when currently assigned to the operator; preserve co-assignees.
  • Revalidate eligibility and assignment before mutation; return conflict for stale state.
  • Accept success only when Gitea confirms recipient present and operator absent.
  • Mobile sheet provides a touch-friendly recipient selector, confirmation, retry status, and removes confirmed handoffs from My Work.
  • Behavioral API/controller tests and full suite pass.
## User problem Mobile operators can release an assigned issue, but cannot transfer ownership to an eligible teammate. Release drops sole-assignee work into the unowned pool and breaks accountability. ## Evidence - `frontend/issue-sheet.js` only exposes `/release` for assignment changes. - `src/gitea_proxy.py::release_assigned_issue` removes the current operator without selecting a successor. - Complete title review (143 issues, 134 PRs) found review-handoff work but no assigned-issue reassignment flow. ## Acceptance - List eligible repository assignees, excluding the current operator and malformed records. - Transfer an open issue only when currently assigned to the operator; preserve co-assignees. - Revalidate eligibility and assignment before mutation; return conflict for stale state. - Accept success only when Gitea confirms recipient present and operator absent. - Mobile sheet provides a touch-friendly recipient selector, confirmation, retry status, and removes confirmed handoffs from My Work. - Behavioral API/controller tests and full suite pass.
timmy was assigned by rockachopa 2026-08-08 08:28:39 +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#281
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?