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

Load mobile issue-filing metadata in one resilient request #847

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

Evidence

Mobile repository selection currently loads labels, milestones, and templates through separate requests. The searchable picker omits templates entirely, while other paths serialize labels before templates. Each server route repeats repository authorization. This makes template availability entry-path dependent and turns one metadata failure into avoidable filing latency.

Deliverable

Add an authenticated aggregate issue-filing metadata route that authorizes once, loads labels/milestones/templates concurrently, and returns section-level availability. Use one stale-response-safe frontend loader for repository selection so searchable, native, and restored-draft paths render healthy sections independently.

Acceptance

  • One request returns labels, open milestones, and issue templates after one repository access check.
  • Metadata loaders begin concurrently and one section failure preserves healthy sections.
  • Search-selected repositories receive templates.
  • A late response for a previously selected repository cannot overwrite the current form.
  • Focused behavioral tests and the full suite pass.

Implementation must use strict RED-GREEN TDD and ship through a linked PR.

## Evidence Mobile repository selection currently loads labels, milestones, and templates through separate requests. The searchable picker omits templates entirely, while other paths serialize labels before templates. Each server route repeats repository authorization. This makes template availability entry-path dependent and turns one metadata failure into avoidable filing latency. ## Deliverable Add an authenticated aggregate issue-filing metadata route that authorizes once, loads labels/milestones/templates concurrently, and returns section-level availability. Use one stale-response-safe frontend loader for repository selection so searchable, native, and restored-draft paths render healthy sections independently. ## Acceptance - One request returns labels, open milestones, and issue templates after one repository access check. - Metadata loaders begin concurrently and one section failure preserves healthy sections. - Search-selected repositories receive templates. - A late response for a previously selected repository cannot overwrite the current form. - Focused behavioral tests and the full suite pass. Implementation must use strict RED-GREEN TDD and ship through a linked PR.
timmy self-assigned this 2026-08-14 19:48:31 +00:00
timmy closed this issue 2026-08-14 20:02:52 +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#847
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?