UI: Add Run ID filter to the Grid view - #70150
Conversation
bbovenzi
left a comment
There was a problem hiding this comment.
Could you show a screenshot of what the filter dropdown, and form look like too?
We're adding run_id pattern and the prefix pattern. We should either use both of them in the UI, with the prefix toggle button or drop the prefix pattern from the API.
@bbovenzi, Ive added more screenshots in the description. I also dropped the prefix pattern from the pr, its not needed. Hope this looks good? |
7d68c6e to
e1d37a3
Compare
|
@bbovenzi, I added back the pattern match, let me know if this is good
|
bbovenzi
left a comment
There was a problem hiding this comment.
LGTM. Let's just rebase and rebuild the API docs
The Dag Runs list page lets users narrow runs by Run ID, but the Grid view's filter bar offered no equivalent, forcing users to eyeball run columns to locate a specific run. Expose the same Run ID search on the Grid so both surfaces filter consistently. The pill exposes the same substring/prefix advanced-search toggle used elsewhere; the Grid query hooks route the value through ``useAdvancedSearchArg`` so the toggle chooses between the substring ``run_id_pattern`` and the index-friendly ``run_id_prefix_pattern`` variant on each request.
4ee0b1f to
2b9994b
Compare
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
The Dag Runs list page lets users narrow runs by Run ID, but the Grid view's filter bar offered no equivalent, forcing users to eyeball run columns to locate a specific run. Expose the same Run ID search on the Grid so both surfaces filter consistently. The pill exposes the same substring/prefix advanced-search toggle used elsewhere; the Grid query hooks route the value through ``useAdvancedSearchArg`` so the toggle chooses between the substring ``run_id_pattern`` and the index-friendly ``run_id_prefix_pattern`` variant on each request. (cherry picked from commit 5197210) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
|
Moving to 3.4.0 this is more suitable for minor as its a new feature |
The Dag Runs list page lets users narrow runs by Run ID, but the Grid view's filter bar offered no equivalent, forcing users to eyeball run columns to locate a specific run. Expose the same Run ID search on the Grid so both surfaces filter consistently. The pill exposes the same substring/prefix advanced-search toggle used elsewhere; the Grid query hooks route the value through ``useAdvancedSearchArg`` so the toggle chooses between the substring ``run_id_pattern`` and the index-friendly ``run_id_prefix_pattern`` variant on each request. (cherry picked from commit 5197210) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>
The Dag Runs list page lets users narrow runs by Run ID, but the Grid view's filter bar offered no equivalent, forcing users to eyeball run columns to locate a specific run. Expose the same Run ID search on the Grid so both surfaces filter consistently. The pill exposes the same substring/prefix advanced-search toggle used elsewhere; the Grid query hooks route the value through ``useAdvancedSearchArg`` so the toggle chooses between the substring ``run_id_pattern`` and the index-friendly ``run_id_prefix_pattern`` variant on each request.






The Dag Runs list page lets users narrow runs by Run ID, but the Grid view's filter bar offered no equivalent — forcing users to eyeball run columns to locate a specific run. This adds the same Run ID search to the Grid view so both surfaces filter consistently.
Additional Screenshots:

Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines