dennis-weyland-by opened a new issue #21493: URL: https://github.com/apache/airflow/issues/21493
### Description Consider the following example: The current datetime is 2022-02-10 09:45 CET and airflow executed two runs: - daily_run scheduled to run every day at 09:43 CET - maintenance triggered manually at 2022-02-10 09:41 CET In the UI it looks like this:  From someone new to airflow there are some unintuitive things for display: - Although both dags ran on the same day, they display different dates in the last run - The DateTime in the Next run column for daily_run is in the past On a technical level, this is documented. Airflow runs its schedule after the schedule interval is completed and what is displayed is the start_date of the interval similar to the start_date parameter of a DAG. As a developer, which works with Airflow, I have to read the documentation and act accordingly. So far this is fine. My point is, that not every consumer of the UI is familiar with Airflow and to some, this is very confusing and counterintuitive. As a developer, I would like to have the option to switch the displayed days to the execution/run after date. This information is also already there when using the info tooltip:   **Summary** Introduce a config flag for the web-server that on the front page the actual time of the future/past execution of a scheduled dag is shown. Since this is a behavior inconsistent with internal airflow behavior, the flag should be disabled by default. **Optional: Extending this to DAg Details page** The Frontpage is not the only place the behavior is shown. So it might make sense that the flag would also change the following examples: **Tree View:** - Upper right: next Run - Calendar Filter - Column Name (and ordering) in Tree View  **Calendar**:  **Are you willing to submit a PR?** My lack of javascript logic prevents me from doing a pr myself, but I would be willing to help on this issue if needed. ### Use case/motivation I use airflow to schedule/orchestrate ML pipelines like model training, predicting, and so on. I want to use the Airflow UI to further enable those pipelines to an audience, which is not accustomed to airflow. It turned out that the current behavior of how dates are displayed (especially with a mix of scheduled and manually triggered tasks) is very confusing for this use case and makes it hard to onboard people as WebUI-only users. ### Related issues _No response_ ### Are you willing to submit a 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]
