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

Support issue capture across all accessible repositories #403

New Issue
Closed
opened 2026-08-09 13:24:54 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 13:24:54 +00:00
Member
Copy Link

Problem

The New issue / Create & start flow treats the first 50 results from GET /user/repos?limit=50 as the complete selection and authorization set. Operators with more than 50 accessible repositories cannot select, load metadata for, or create an issue in a repository beyond page one.

Evidence

  • src/gitea_proxy.py requests user/repos?limit=50 without pagination.
  • src/main.py truncates context repositories and uses that same list for milestone, label, and create-route access checks.
  • frontend/dashboard.js builds the capture selector only from initial context.
  • Historical issue/PR and commit-title review found pagination work for My Work, Find Work, and notifications, but none for issue capture repositories.

Acceptance criteria

  • Initial capture remains fast with the first repository page.
  • Users can load later pages without duplicate options or losing draft fields/selection.
  • Repositories beyond page one can load labels/milestones and create or Create & start issues.
  • Server authorization uses a targeted repository access check and rejects inaccessible repositories before mutation.
  • A transient next-page failure preserves current options and draft and supports retry.
  • Existing <=50-repository and offline draft behavior remains intact.
## Problem The New issue / Create & start flow treats the first 50 results from `GET /user/repos?limit=50` as the complete selection and authorization set. Operators with more than 50 accessible repositories cannot select, load metadata for, or create an issue in a repository beyond page one. ## Evidence - `src/gitea_proxy.py` requests `user/repos?limit=50` without pagination. - `src/main.py` truncates context repositories and uses that same list for milestone, label, and create-route access checks. - `frontend/dashboard.js` builds the capture selector only from initial context. - Historical issue/PR and commit-title review found pagination work for My Work, Find Work, and notifications, but none for issue capture repositories. ## Acceptance criteria - Initial capture remains fast with the first repository page. - Users can load later pages without duplicate options or losing draft fields/selection. - Repositories beyond page one can load labels/milestones and create or Create & start issues. - Server authorization uses a targeted repository access check and rejects inaccessible repositories before mutation. - A transient next-page failure preserves current options and draft and supports retry. - Existing <=50-repository and offline draft behavior remains intact.
timmy was assigned by rockachopa 2026-08-09 13:24:54 +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#403
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?