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

Open assigned pull requests from mobile Search #785

New Issue
Closed
opened 2026-08-14 00:20:18 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 00:20:18 +00:00
Owner
Copy Link

User problem

Mobile Search can find and preview pull requests, but every pull-request preview is read-only even when the pull request is already assigned to the authenticated operator. The operator must leave Stackchain for Gitea despite an existing native My Work pull-request workspace.

Scope

  • Show Open in My Work for an open pull request assigned to the current operator.
  • Reuse the canonical native pull-request route and sheet without mutating assignment.
  • Preserve the Search route/query underneath so browser Back returns to the same Search session.
  • Keep non-assigned pull requests read-only with the existing Gitea fallback.

Acceptance tests

  • Assigned pull previews expose the native handoff; unassigned pulls remain read-only.
  • Handoff resolves the matching My Work pull and opens its canonical route exactly once.
  • Browser Back restores Search with its query/result session.
  • Existing issue claim/start behavior remains unchanged.
  • Focused Search/My Work/history tests and the full suite pass.

Evidence

origin/main currently restricts the preview CTA to assigned_to_me && kind === issue, while the backend preview already reports assigned_to_me for both issues and pulls and My Work already supports canonical pull routes. Historical issue/PR titles and recent commits contain Search preview, Search resumability, and native PR workflows, but no assigned-PR Search-to-My-Work handoff.

## User problem Mobile Search can find and preview pull requests, but every pull-request preview is read-only even when the pull request is already assigned to the authenticated operator. The operator must leave Stackchain for Gitea despite an existing native My Work pull-request workspace. ## Scope - Show **Open in My Work** for an open pull request assigned to the current operator. - Reuse the canonical native pull-request route and sheet without mutating assignment. - Preserve the Search route/query underneath so browser Back returns to the same Search session. - Keep non-assigned pull requests read-only with the existing Gitea fallback. ## Acceptance tests - Assigned pull previews expose the native handoff; unassigned pulls remain read-only. - Handoff resolves the matching My Work pull and opens its canonical route exactly once. - Browser Back restores Search with its query/result session. - Existing issue claim/start behavior remains unchanged. - Focused Search/My Work/history tests and the full suite pass. ## Evidence `origin/main` currently restricts the preview CTA to `assigned_to_me && kind === issue`, while the backend preview already reports `assigned_to_me` for both issues and pulls and My Work already supports canonical pull routes. Historical issue/PR titles and recent commits contain Search preview, Search resumability, and native PR workflows, but no assigned-PR Search-to-My-Work handoff.
timmy closed this issue 2026-08-14 00:27:41 +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
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#785
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?