UI: Add Select Recent Configurations dropdown to Trigger Dag form by josix · Pull Request #70413 · apache/airflow

josix · 2026-07-24T18:44:17Z

Context

According to the #69820's description, reusing a past run's config currently requires leaving the trigger flow to hunt for the right run in the run list and use "Trigger again with this config". In this PR, I'm going to restore the Airflow 2 in-form dropdown lets users pick any distinct config from the recent runs in a scrollable list while composing a run. The dropdown reuses the existing dagRuns list endpoint and the same conf-only prefill path as the menu item, so no new API surface is added.

closes: #69820

Verification

Was generative AI tooling used to co-author this PR?

Yes

Generated-by: Claude Code following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

pierrejeambrun

Thanks a lot,

A couple suggestions before this can move forward :)

josix · 2026-09-22T14:20:03Z

Hello @pierrejeambrun, thank you for the kind review. I've addressed the issues you pointed out. Please take a look when you have chance Thank you so much!

bbovenzi

One last change

Reusing a past run's config currently requires leaving the trigger flow to hunt for the right run in the run list and use "Trigger again with this config". Restoring the Airflow 2 in-form dropdown lets users pick any distinct config from the recent runs in a scrollable list while composing a run. The dropdown reuses the existing dagRuns list endpoint and the same conf-only prefill path as the menu item, so no new API surface is added. closes: apache#69820

Main now separates React imports from third-party ones, and prettier flags the file otherwise.

Picking a recent configuration reused the re-trigger prefill path, which resets the whole form. A user who had already set a logical date, run id, note or manual data interval lost all of them. The dropdown is meant to swap only the run's conf, so it now leaves every other field untouched.

"Trigger again with this config" already fills the form with one specific run's conf, so showing an unselected recent-configurations dropdown on top of it is contradictory.

The dropdown rendered inside the Trigger Dag modal was clipped at the modal edge because its content stayed inside the modal's DOM tree. The shared Select from src/system-components portals its content and already renders the control, indicator and positioner, so the hand-rolled Chakra parts only duplicated those layers. The trigger form tests also follow main, where the i18n mock returns keys and TriggerDAGForm no longer takes dagDisplayName.

josix · 2026-10-10T10:36:28Z

Thanks for the review @bbovenzi! Addressed all three comments in the latest push: RecentConfigSelect now uses Select from src/system-components, so the dropdown is portalled and no longer cut off by the modal. The trigger is just Select.Trigger with Select.ValueText, and the extra Select.Positioner is gone now.

bbovenzi · 2026-10-13T20:14:31Z

E2e test failure is unrelated

github-actions · 2026-10-18T08:58:33Z

Backport successfully created: v3-4-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-4-test

…Dag form (#70413) (#74977) * UI: Add Select Recent Configurations dropdown to Trigger Dag form Reusing a past run's config currently requires leaving the trigger flow to hunt for the right run in the run list and use "Trigger again with this config". Restoring the Airflow 2 in-form dropdown lets users pick any distinct config from the recent runs in a scrollable list while composing a run. The dropdown reuses the existing dagRuns list endpoint and the same conf-only prefill path as the menu item, so no new API surface is added. closes: #69820 * UI: Regroup imports in RecentConfigSelect after rebase Main now separates React imports from third-party ones, and prettier flags the file otherwise. * UI: Keep user input when selecting a recent configuration Picking a recent configuration reused the re-trigger prefill path, which resets the whole form. A user who had already set a logical date, run id, note or manual data interval lost all of them. The dropdown is meant to swap only the run's conf, so it now leaves every other field untouched. * UI: Hide recent configurations when re-triggering with a run's config "Trigger again with this config" already fills the form with one specific run's conf, so showing an unselected recent-configurations dropdown on top of it is contradictory. * UI: Use system Select for the recent configurations dropdown The dropdown rendered inside the Trigger Dag modal was clipped at the modal edge because its content stayed inside the modal's DOM tree. The shared Select from src/system-components portals its content and already renders the control, indicator and positioner, so the hand-rolled Chakra parts only duplicated those layers. The trigger form tests also follow main, where the i18n mock returns keys and TriggerDAGForm no longer takes dagDisplayName. (cherry picked from commit 6fc06c6) Co-authored-by: Wilson Josix Wang <josixwang@gmail.com>

josix requested review from bbovenzi, choo121600, guan404ming, pierrejeambrun, ryanahamilton, shubhamraj-git and vatsrahul1001 as code owners July 24, 2026 18:44

boring-cyborg Bot added area:translations area:UI Related to UI/UX. For Frontend Developers. translation:default labels Jul 24, 2026

josix force-pushed the add-recent-config-dropdown-trigger-form branch from c95038e to 632e715 Compare July 24, 2026 18:48

josix marked this pull request as draft July 24, 2026 18:53

josix force-pushed the add-recent-config-dropdown-trigger-form branch from 632e715 to 1c782ec Compare July 24, 2026 19:03

josix marked this pull request as ready for review July 24, 2026 19:23

pierrejeambrun reviewed Aug 21, 2026

View reviewed changes

Comment thread airflow-core/src/airflow/ui/src/components/TriggerDag/RecentConfigSelect.tsx

Comment thread airflow-core/src/airflow/ui/src/components/TriggerDag/RecentConfigSelect.tsx Outdated

josix force-pushed the add-recent-config-dropdown-trigger-form branch from 1c782ec to 9439987 Compare September 22, 2026 13:55

josix requested a review from pierrejeambrun September 22, 2026 14:15

This was referenced Sep 22, 2026

Add split-button caret to Trigger DAG button #73564

Closed

dropdown to the Trigger DAG has dramatically decrease UX #73177

Closed

bbovenzi added this to the Airflow 3.4.0 milestone Sep 29, 2026

bbovenzi reviewed Sep 29, 2026

View reviewed changes

josix added 5 commits October 10, 2026 17:43

UI: Regroup imports in RecentConfigSelect after rebase

e20b3ac

Main now separates React imports from third-party ones, and prettier flags the file otherwise.

UI: Hide recent configurations when re-triggering with a run's config

1e384fc

"Trigger again with this config" already fills the form with one specific run's conf, so showing an unselected recent-configurations dropdown on top of it is contradictory.

josix force-pushed the add-recent-config-dropdown-trigger-form branch from 9439987 to af7f357 Compare October 10, 2026 10:29

josix requested a review from bbovenzi October 10, 2026 10:36

bbovenzi approved these changes Oct 13, 2026

View reviewed changes

bbovenzi merged commit 6fc06c6 into apache:main Oct 13, 2026
87 of 88 checks passed

josix mentioned this pull request Oct 20, 2026

Add josix's July to October contribution report for apache-airflow opensource4you/readme#55

Merged

vatsrahul1001 mentioned this pull request Oct 28, 2026

Status of testing of Apache Airflow 3.4.0rc1 #75865

Open

Navigation Menu

Repository navigation

UI: Add Select Recent Configurations dropdown to Trigger Dag form - #70413

UI: Add Select Recent Configurations dropdown to Trigger Dag form#70413
bbovenzi merged 5 commits into
apache:mainfrom
josix:add-recent-config-dropdown-trigger-form

josix commented Jul 24, 2026 •

edited

Loading

Uh oh!

pierrejeambrun left a comment

Uh oh!

Uh oh!

Uh oh!

josix commented Sep 22, 2026

Uh oh!

bbovenzi left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

josix commented Oct 10, 2026

Uh oh!

bbovenzi commented Oct 13, 2026

Uh oh!

Uh oh!

github-actions Bot commented Oct 18, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

josix commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Context

Verification

Was generative AI tooling used to co-author this PR?

Uh oh!

pierrejeambrun left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

josix commented Sep 22, 2026

Uh oh!

bbovenzi left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

josix commented Oct 10, 2026

Uh oh!

bbovenzi commented Oct 13, 2026

Uh oh!

Uh oh!

github-actions Bot commented Oct 18, 2026

Backport successfully created: v3-4-test

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

josix commented Jul 24, 2026 •

edited

Loading