travis-cook-sfdc opened a new issue, #32751:
URL: https://github.com/apache/airflow/issues/32751

   ### Apache Airflow version
   
   2.6.3
   
   ### What happened
   
   In the old tree view, all of columns for each run would display the 
`data_interval_start` / date from the `run_id` as the UI identifier for the dag 
run.
   
   In the new grid view, it's inconsistent.
   
   For example, the header of this column says `2023-07-17 00:00:00`:
   <img width="77" alt="image" 
src="https://github.com/apache/airflow/assets/119886245/8386f886-bfe9-4c93-b35a-334a4a1d28eb";>
   
   But when you hover over the same DAG Run, it display the `Data Interval End` 
date of `2023-07-18 00:00:00`: 
   <img width="511" alt="image" 
src="https://github.com/apache/airflow/assets/119886245/8614b289-cc88-4e63-be6a-3e247178ffeb";>
   
   This inconsistency is causing confusion for users of Airflow because they're 
just not sure what date is being processed.
   
   ### What you think should happen instead
   
   In order to retain consistency they should show the same value.
   
   I think in order to maintain parity with the old tree view and the run_id, 
it should display the `data_interval_start` in the tooltip.
   
   ### How to reproduce
   
   1. Navigate to grid view for any DAG.
   2. See the discrepancy between the column header and the tooltip's date 
values for a `"@daily"` job.
   
   ### Operating System
   
   Debian GNU/Linux
   
   ### Versions of Apache Airflow Providers
   
   N/A
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### 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]

Reply via email to