Answer: No — the floating job list on the commits page is not searchable today.

That popup is the commit build-status dropdown (JobListPanel). It lists every job for the commit with no search/filter box and does not auto-focus an input. There is no setting or workaround that makes it searchable.

Related existing behavior: the separate Run Job selector already has a search field with case-insensitive substring filtering (and keyboard select-by-typing). That is a different UI from the floating commit-status job list.

The same non-searchable panel is also used from other commit-status entry points (branches, tags, file browser, commit detail) and on the build detail page.

Before opening an Improvement issue for this, a few high-level choices:

1. Where should search apply?

   • A. Only the commits page floating job list
   • B. All commit-status job popups (commits, branches, tags, file browser, commit detail) — same component
   • C. All of B, plus the job list on the build detail page
   • Pros: A is smallest scope. Cons: A/B leave the same list searchable in some places and not others.
   • Recommendation: C — one searchable list everywhere that panel appears.

2. When should the search box appear / take focus?

   • A. Always show search and auto-focus it when the popup opens
   • B. Only when job count exceeds a threshold (e.g. 10+); otherwise keep today’s behavior
   • C. Always show search, but auto-focus only above a threshold
   • Pros: A is fastest for ~30-job setups. Cons: always auto-focusing can feel noisy for short lists.
   • Recommendation: C with a threshold around 8–10.

3. Matching style?

   • A. Case-insensitive substring (same as today’s Run Job selector) — e.g. prod matches deploy-prod-eu
   • B. Multi-token “smart” match: whitespace-separated tokens must each match as substrings in order (your op prod idea) without full regex
   • C. Treat the input as a regex (e.g. op.+prod)
   • Pros: A is consistent/simple; B covers the bonus case with less surprise than regex. Cons: C is powerful but easy to mistype.
   • Recommendation: B (single token behaves like A).

4. Empty filter result?

   • A. Show a simple empty / “No jobs” state in the popup
   • B. Keep showing the unfiltered list when nothing matches
   • Recommendation: A.

@zaakiy Reply with your choices (e.g. 1C 2C 3B 4A), or say the recommendations are fine as-is, and I’ll open a related Improvement issue with that requirement.

1. c
2. a
3. b
4. a

@servicedesk CC @robin

Answered: the floating job list is not searchable today; follow-up tracked in #2896.

Recorded your choices as 1C 2A 3B 4A. Opened improvement #2896 with that requirement and linked it as related.