roshankp opened a new issue #18365:
URL: https://github.com/apache/airflow/issues/18365
### Apache Airflow version
2.1.3
### Operating System
macosx
### Versions of Apache Airflow Providers
apache-airflow==1!2.1.3+astro.1
apache-airflow-providers-amazon==2.1.0
apache-airflow-providers-celery==2.0.0
apache-airflow-providers-databricks==2.0.0
apache-airflow-providers-ftp==2.0.0
apache-airflow-providers-google==5.0.0
apache-airflow-providers-http==2.0.0
apache-airflow-providers-imap==2.0.0
apache-airflow-providers-microsoft-mssql==2.0.0
apache-airflow-providers-mysql==2.1.0
apache-airflow-providers-opsgenie==2.0.0
apache-airflow-providers-postgres==2.0.0
apache-airflow-providers-sftp==2.1.0
apache-airflow-providers-slack==4.0.0
apache-airflow-providers-snowflake==2.1.0
apache-airflow-providers-sqlite==2.0.0
apache-airflow-providers-ssh==2.1.0
### Deployment
Astronomer
### Deployment details
Astro version 2.1.3
### What happened
Recently upgraded the platform to 2.1.3 and observed issues with
TriggerDagRunOperator Operator. The child dag object when triggered from parent
dag is not showing the start time in the tree view.
Also start time are showing up as null in dag_run table.
trigger_profile = TriggerDagRunOperator(
task_id='trigger_profile', trigger_dag_id='child_dag'
)

### What you expected to happen
ideally it should display timestamp.
### How to reproduce
- create two DAGS.
- dag_main.py
- dag_child.py
- create an operator in dag_main.py
- trigger_dag_child = TriggerDagRunOperator(
task_id='trigger_profile', trigger_dag_id='dag_child'
)
- check start time in child dag
### 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]