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

Search the full Find Work catalog and preserve batch selections #673

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

Problem

Find Work exposes a globally ranked catalog of up to 500 unassigned issues, but the mobile sheet can only page through 50-card chunks. Operators who know a repository, issue number, or title must repeatedly load and scan pages before they can use the existing batch-claim flow.

Product slice

Add server-backed, case-insensitive search across the complete retained catalog before pagination. Search repository identity, #number/number, and title. Add a mobile-safe search/Clear row, latest-response-wins request handling, truthful match counts, and preserve explicit batch selections across query changes.

Acceptance criteria

  • A query matches repository, issue number, or title outside the first unfiltered page.
  • Filtering happens before 50-item pagination and preserves catalog priority order.
  • Rapid query changes cannot render an older response; Clear restores the full catalog.
  • Selected work remains selected across queries so a cross-query batch can be claimed.
  • Search and batch controls remain phone-reachable with 44px targets.
  • Focused behavioral tests and the full suite pass.

Evidence / non-duplication

Current origin/main at dcf26c8 has pagination and batch claim (#671/#672), while owned-queue search (#667/#668) applies only to My Work. Inspection of 339 historical issue titles, six open issues, zero open PRs, and recent commits found no search for the unassigned Find Work catalog.

## Problem Find Work exposes a globally ranked catalog of up to 500 unassigned issues, but the mobile sheet can only page through 50-card chunks. Operators who know a repository, issue number, or title must repeatedly load and scan pages before they can use the existing batch-claim flow. ## Product slice Add server-backed, case-insensitive search across the complete retained catalog before pagination. Search repository identity, `#number`/number, and title. Add a mobile-safe search/Clear row, latest-response-wins request handling, truthful match counts, and preserve explicit batch selections across query changes. ## Acceptance criteria - A query matches repository, issue number, or title outside the first unfiltered page. - Filtering happens before 50-item pagination and preserves catalog priority order. - Rapid query changes cannot render an older response; Clear restores the full catalog. - Selected work remains selected across queries so a cross-query batch can be claimed. - Search and batch controls remain phone-reachable with 44px targets. - Focused behavioral tests and the full suite pass. ## Evidence / non-duplication Current `origin/main` at `dcf26c8` has pagination and batch claim (#671/#672), while owned-queue search (#667/#668) applies only to My Work. Inspection of 339 historical issue titles, six open issues, zero open PRs, and recent commits found no search for the unassigned Find Work catalog.
timmy self-assigned this 2026-08-12 19:18:53 +00:00
timmy closed this issue 2026-08-12 19:27:11 +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#673
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?