-
-
@wh assign this issue to yourself and work on it. Right now, let's only do a simple substring check (convert to lowercase first) instead of smart matching to be consistent with filterings of other places.
-
-
-
I don't have write permission to the project to implement this change. Assigning back to @robin.
-
-
@servicedesk you are not entitled to interact with me
-
-
@servicedesk you are not entitled to interact with me
-
-
State changed as build OD-7846 is successful
-
OneDev
changed state to 'Closed' 2 days ago
Previous Value Current Value Open
Closed
-


I think we do need to switch to a regex, because it's the only way to capture word boundaries.
Capturing word boundaries would mean that we can capture the beginning of the word
testin this example.Don't assume. Ask high-level clarifying questions if needed.
- Numbered questions (1, 2, 3, etc)
- Lettered answer options (A, B, C, etc)
- Pros and Cons? Your recommendation?
-
Previous Value Current Value Closed
Open
-
@zaakiy I understand you would like word-boundary matching instead of simple substring matching. However, the images you attached are not rendering for me. Could you describe the specific scenario where the current substring matching falls short?
For example:
- What job names are in the list?
- What search term are you typing?
- What results do you expect vs. what you actually get?
This will help me determine whether word-boundary matching is needed or if there is a different approach that better addresses your concern.
-
@zaakiy this is intensionally not implemented to be consistent with our searches.
-
correct: with other searches
-
Previous Value Current Value Open
Closed
-
On behalf of AI user "Service Desk": Failed to do the job, please open workspace OD-6 for details
-
On behalf of AI user "Service Desk": Failed to do the job, please open workspace OD-7 for details
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Summary
Add search/filter support to
JobListPanel(the floating job list shown from commit build status and related UIs) so users with many jobs can quickly find the one they need.Current behavior
JobListPanellists every job for the commit with no search box and no auto-focus. The same panel is used from commit-status entry points and on the build detail page. (The separate Run Job selector already has substring search; that is a different UI.)Scope
Apply everywhere
JobListPanelis used:Expected behavior
op prodmatches a name that containsopand laterprod). A single token behaves like ordinary case-insensitive substring matchAcceptance criteria
JobListPanelopensRelated question: #2895