-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Closed
Labels
affected_version:3.1Issues Reported for 3.1Issues Reported for 3.1area:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.good first issuekind:bugThis is a clearly a bugThis is a clearly a bug
Description
Apache Airflow version
3.1.0
If "Other Airflow 2/3 version" selected, which one?
3.0.0 onwards
What happened?
For the airflow 3 versions, when the dag schedule is based on an asset with the longer name, the name of the asset extends to overlap with the last run field and makes it hard to read the timestamp of the last run , for the user .
What you think should happen instead?
The name of the assets should be handled in such a way that the field values don't overlap with each other
How to reproduce
- Deploy the dags with asset based schedule to airflow version 3.0.0 based deployment
- Run the dags and verify if the name of the asset overlaps the last run field
Operating System
os
Versions of Apache Airflow Providers
Official Apache Airflow Helm Chart
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else?
Related to #55721
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
affected_version:3.1Issues Reported for 3.1Issues Reported for 3.1area:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.good first issuekind:bugThis is a clearly a bugThis is a clearly a bug