Repository navigation
Trigger DAG modal: two-column layout for params (label left, control right) #67852
Description
Description
In the AF3 Trigger DAG form, each param is rendered on a single row: the field label and the control sit inline. For boolean params, the toggle appears immediately after the label text. When labels differ in length, toggles and other controls do not share a common right edge, so the form is harder to scan than a classic label/control grid.
In Airflow 2.x, the FAB trigger form used a two-column layout: label on the left, control on the right, with controls aligned in a dedicated column. That right-aligned control column made boolean toggles easy to compare at a glance, especially for DAGs with many params.
Airflow 2:
Airflow 3:
Use case/motivation
We trigger DAGs from the UI with many boolean params (e.g. selecting which integration tests to run). Operators need to flip several toggles quickly without hunting for each switch along an uneven line.
A consistent label column + right-aligned control column would match how the AF2 trigger UI behaved and would improve daily use for any DAG with more than a handful of params, not only test runners.
Related issues
- Trigger DAG modal: long param names overflow modal width #67851
- AF3 FlexibleForm introduction: Migrate trigger form params to new UI #45270
- Trigger form wire-up: Connect Trigger UI Conf with the flexible form #45790
- AIP-50 (FAB trigger UI): https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-50+Trigger+DAG+UI+Extension+with+Flexible+User+Form+Concept
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
Codingaditya17 commentedon Jun 2, 2026
Hi, I would like to work on this if no one is actively taking it.
My plan is to update the AF3 Trigger DAG params layout so labels and controls render in a consistent two-column grid, with labels on the left and controls aligned in a dedicated right column. I will also make sure long param names still wrap/overflow safely and do not regress the related modal width issue.
venkatamandavilli-code commentedon Jun 17, 2026
Thanks for raising this enhancement.
I agree that a two-column layout would improve usability, particularly for DAGs with a large number of parameters. When operators trigger workflows that contain multiple boolean options, dropdowns, or configuration fields, consistent alignment of controls makes the form easier to scan and reduces the effort required to locate and update values.
The Airflow 2.x layout provided a clearer visual separation between labels and inputs, which helped users compare and modify settings more efficiently. With the current inline layout, controls can appear uneven when parameter names vary in length, making the form feel more cluttered as the number of parameters grows.
From an operational perspective, this would be especially helpful for teams that frequently trigger DAGs from the UI and need to adjust multiple parameters during testing, troubleshooting, or controlled production executions.
I think restoring a dedicated label column and aligned control column would improve readability while maintaining compatibility with the newer flexible form approach.