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

Hand off assigned pull requests and continue Today #567

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

Problem

Assigned pull requests support reading, discussion, review, defer, and merge on mobile, but not releasing or transferring ownership. Operators must leave Stackchain for Gitea and then manually recover their Today flow.

Scope

  • Add bounded eligible teammate discovery for assigned pull requests.
  • Add confirmed release and handoff operations that preserve co-assignees and mutate only the current operator.
  • Add online-only ownership controls to the pull sheet.
  • On confirmed ownership exit, remove the pull from My Work/Today and continue to the next ready item.

Acceptance

  • Closed, merged, unassigned, and ineligible-recipient requests fail without mutation.
  • Handoff preserves co-assignees, removes the current operator, and adds the recipient exactly once; release only removes the current operator.
  • Success is reported only after canonical assignee confirmation.
  • Failed or ambiguous confirmation keeps the pull visible with retry guidance.
  • Offline controls are inert and truthful.
  • At 390x844 and 320x568, ownership controls remain reachable without horizontal overflow and have accessible status/focus behavior.
  • Behavioral API/frontend tests and the full suite pass.

No historical issue title or recent commit covers pull-request ownership transfer; #183, #281, and #449 are issue-only ownership flows.

## Problem Assigned pull requests support reading, discussion, review, defer, and merge on mobile, but not releasing or transferring ownership. Operators must leave Stackchain for Gitea and then manually recover their Today flow. ## Scope - Add bounded eligible teammate discovery for assigned pull requests. - Add confirmed release and handoff operations that preserve co-assignees and mutate only the current operator. - Add online-only ownership controls to the pull sheet. - On confirmed ownership exit, remove the pull from My Work/Today and continue to the next ready item. ## Acceptance - Closed, merged, unassigned, and ineligible-recipient requests fail without mutation. - Handoff preserves co-assignees, removes the current operator, and adds the recipient exactly once; release only removes the current operator. - Success is reported only after canonical assignee confirmation. - Failed or ambiguous confirmation keeps the pull visible with retry guidance. - Offline controls are inert and truthful. - At 390x844 and 320x568, ownership controls remain reachable without horizontal overflow and have accessible status/focus behavior. - Behavioral API/frontend tests and the full suite pass. No historical issue title or recent commit covers pull-request ownership transfer; #183, #281, and #449 are issue-only ownership flows.
timmy self-assigned this 2026-08-11 11:22:21 +00:00
timmy closed this issue 2026-08-11 12:40:17 +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#567
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?