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

Scope mobile Search to an accessible repository #795

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

Product problem

Global Search currently spans every accessible repository, so common queries produce noisy cross-repository results even when the operator knows where the work lives. Type and status filters shipped in #793, but repository context is only displayed after results arrive.

Vertical slice

Add an accessible-repository filter to mobile Search. Repository lookup must use the existing visible-repository endpoint; selected scope must compose with type/status, apply to every result page, survive preview/Back and shared URL restoration, and clear back to organization-wide Search. Stale lookup/search responses must not replace the active scope.

Acceptance

  • Search and select an accessible repository from the Search workspace on a phone-sized viewport.
  • Exact repository scope reaches issue and pull search, including later pages.
  • Repository, type, and status restore across preview/Back and share URL.
  • Clearing repository restores organization-wide results.
  • Invalid scope is rejected without upstream detail leakage.
  • Focused behavioral tests and full suite pass.

Audit evidence: current origin/main 7636e30 sends only q/kind/state; exhaustive review of 401 historical issue titles and recent commits found no repository-scoped global Search work. Related #487 applies only to issue capture and #681 only to Find Work.

## Product problem Global Search currently spans every accessible repository, so common queries produce noisy cross-repository results even when the operator knows where the work lives. Type and status filters shipped in #793, but repository context is only displayed after results arrive. ## Vertical slice Add an accessible-repository filter to mobile Search. Repository lookup must use the existing visible-repository endpoint; selected scope must compose with type/status, apply to every result page, survive preview/Back and shared URL restoration, and clear back to organization-wide Search. Stale lookup/search responses must not replace the active scope. ## Acceptance - Search and select an accessible repository from the Search workspace on a phone-sized viewport. - Exact repository scope reaches issue and pull search, including later pages. - Repository, type, and status restore across preview/Back and share URL. - Clearing repository restores organization-wide results. - Invalid scope is rejected without upstream detail leakage. - Focused behavioral tests and full suite pass. Audit evidence: current `origin/main` 7636e30 sends only q/kind/state; exhaustive review of 401 historical issue titles and recent commits found no repository-scoped global Search work. Related #487 applies only to issue capture and #681 only to Find Work.
timmy closed this issue 2026-08-14 03:14:07 +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#795
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?