rebel-wansoo opened a new issue, #56575: URL: https://github.com/apache/airflow/issues/56575
### Apache Airflow version 3.1.0 ### If "Other Airflow 2/3 version" selected, which one? _No response_ ### What happened? Webserver setting: AIRFLOW__WEBSERVER__GRID_VIEW_SORTING_ORDER=topological DAG structure: multi-level DAG using @task_group Even when the configuration option grid_view_sorting_order=topological is set, the vertical order of tasks and task groups in Grid View does not match the actual topological (execution) order of the DAG. The Graph View and execution dependencies are correct, but the Grid View’s left-hand task list appears to be sorted alphabetically by task_id / group_id. Example DAG structure: start >> step_a >> step_b >> finish Expected topological order (execution order): start → step_a → step_b → finish Actual order shown in Grid View: finish start step_a step_b Expected Behavior When grid_view_sorting_order=topological is used, the vertical task order in Grid View should match the DAG’s topological execution order. Expected display: start step_a step_b finish Grid View appears to sort sibling tasks/groups alphabetically rather than following topological order. Graph View and runtime behavior are correct; only the Grid View ordering is inconsistent. ### What you think should happen instead? _No response_ ### How to reproduce Create a simple DAG: start >> step_a >> step_b >> finish Set environment variable: AIRFLOW__WEBSERVER__GRID_VIEW_SORTING_ORDER=topological Run the DAG and open Grid View. Observe that the left-hand task list does not follow topological order. ### Operating System Ubuntu 22.04.5 LTS ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
