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

Surface authored pull requests in My Work #1346

New Issue
Closed
opened 2026-08-24 10:53:20 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-24 10:53:20 +00:00
Member
Copy Link

User problem

The mobile My Work experience cannot discover open pull requests authored by the signed-in operator unless they are also assigned or awaiting that operator's review. Recent draft, context, feedback, reviewer, and merge actions therefore remain hidden behind global search or notifications for a normal PR author.

Vertical slice

Add authored pull requests as an authoritative, deduplicated My PRs queue in My Work. Fetch the created-pull stream alongside existing assigned/review-requested streams, preserve partial-failure truth, classify authored ownership in the API model, expose the queue in the mobile launcher, and route rows into the existing pull workspace.

Acceptance tests

  • An open pull authored by the signed-in user appears even when neither assigned nor review-requested.
  • A pull that is both authored and assigned appears once and preserves both reasons.
  • Failure of only the authored-pull source marks that source unavailable without hiding assigned/review-requested work.
  • My PRs is available from the mobile queues sheet, reports an accurate count, opens the existing pull route, and has 44px touch controls with no 320px horizontal overflow.
  • Server, frontend unit, focused browser journey, and full regression suites pass.

Evidence / non-duplication

src/gitea_proxy.py currently searches assigned issues, authored issues, assigned pulls, and requested reviews, but no created pull stream. src/main.py retains only assigned/review-requested reasons for pull items. None of 676 historical issue titles, the eight current open issues, open PR #1282, or recent main commits cover authored-PR discovery; recent work #1330–#1344 adds actions inside pull detail rather than discovery.

## User problem The mobile **My Work** experience cannot discover open pull requests authored by the signed-in operator unless they are also assigned or awaiting that operator's review. Recent draft, context, feedback, reviewer, and merge actions therefore remain hidden behind global search or notifications for a normal PR author. ## Vertical slice Add authored pull requests as an authoritative, deduplicated **My PRs** queue in My Work. Fetch the created-pull stream alongside existing assigned/review-requested streams, preserve partial-failure truth, classify authored ownership in the API model, expose the queue in the mobile launcher, and route rows into the existing pull workspace. ## Acceptance tests - An open pull authored by the signed-in user appears even when neither assigned nor review-requested. - A pull that is both authored and assigned appears once and preserves both reasons. - Failure of only the authored-pull source marks that source unavailable without hiding assigned/review-requested work. - **My PRs** is available from the mobile queues sheet, reports an accurate count, opens the existing pull route, and has 44px touch controls with no 320px horizontal overflow. - Server, frontend unit, focused browser journey, and full regression suites pass. ## Evidence / non-duplication `src/gitea_proxy.py` currently searches assigned issues, authored issues, assigned pulls, and requested reviews, but no created pull stream. `src/main.py` retains only assigned/review-requested reasons for pull items. None of 676 historical issue titles, the eight current open issues, open PR #1282, or recent main commits cover authored-PR discovery; recent work #1330–#1344 adds actions inside pull detail rather than discovery.
timmy was assigned by rockachopa 2026-08-24 10:53:20 +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#1346
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?