AetherUnbound opened a new issue, #39179: URL: https://github.com/apache/airflow/issues/39179
### Apache Airflow version 2.9.0 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? See https://github.com/WordPress/openverse/pull/4176 for a specific case. When viewing a URL generated by `TaskInsatnce::log_url`, this directs the user to a `/log` page. This page has the DAG ID and the enable/disable switch at the top, but no link to get to the DAG's grid or graph view. Additionally, the `schedule` information in the top right of the page will always show as `Schedule: False` on the `/log` page, even if the DAG has a schedule. The "Log Url" that shows up in the "Task Instances" browse page of the webserver apparently uses a link to the grid view rather than `/log` directly. ### What you think should happen instead? It would be helpful if the `/log` page (and thus the link generated by `TaskInstance::log_url`) had a way to view the entire DAG in the graph & grid views. So much work has been done on the new DAG view (which rocks!) - that would be the ideal view to be directed to IMO rather than a standalone log page that requires navigation to the DAGs list then navigation to the DAG _then_ navigation to the right DAG run and task in order to actually view the failure in the context of the entire DAG. ### How to reproduce Run a task which prints out `ti.log_url`, then visit that URL and observe that there's no way to navigate back to the DAG. ### Operating System Official docker image ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [X] 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]
