ljades opened a new issue #19264: URL: https://github.com/apache/airflow/issues/19264
### Apache Airflow version 2.2.0 (latest released) ### Operating System Debian ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details Using base Docker image astronomerinc/ap-airflow:2.0.2-2-buster. ### What happened The [TriggerDagRunOperator](https://airflow.apache.org/docs/apache-airflow/stable/_api/airflow/operators/trigger_dagrun/index.html) embeds an external link that links to the DAG that's being triggered. The problem is, the link currently includes a parameter for restricting to execution dates EARLIER than the execution date of the triggering DAG itself. This means that the external link is always guaranteed to not link to the right DAG run (and not even show it as an option until you manually change the execution date filter in the new page). It links to the DAG page but never to the right instance without some manual tampering after clicking on the link. ### What you expected to happen The Triggered DAG should point to the execution date of the triggered dag, not the triggerING DAG. If this is not feasible, it should at least point to the Triggered DAG page with no execution date constraints. At least this would show the latest run, and it will include in the dropdown the triggered run. ### How to reproduce Create a DAG with a TriggerDagRunOperator that triggers another DAG. Run the former DAG, wait for the task to run. Click on the task, click on the "Triggered DAG" external link. It will not show the triggered run that just happened. You will need to manually adjust the date constraint in the upper left of the DAG views, and then select your run. ### 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]
