jayachandrakasarla opened a new pull request, #68378: URL: https://github.com/apache/airflow/pull/68378
Closes: #67971 ## What This PR enhances the Airflow 3 Task Instance Details page by surfacing additional task instance metadata that was previously available in Airflow 2. A new **Additional Task Instance Attributes** section has been added to the Details view, displaying: * Try Number * Max Tries * DAG ID * Trigger * Triggerer Job The PR also adds the corresponding translation strings for the new UI labels. ## Why Airflow 3 exposes task retry history through the try selector, but some task instance metadata is not easily discoverable from the Details view. This change surfaces additional task instance attributes such as Max Tries, DAG ID, Trigger, and Triggerer Job, making task debugging and troubleshooting easier while restoring information that was previously available in Airflow 2. ## Testing Tested locally using Breeze and the Airflow UI. Verified: * Successful task instances display the new attributes section. * Retrying tasks display updated Try Number and Max Tries values. * Deferrable sensor tasks correctly surface Trigger and Triggerer Job information when applicable. * Existing task details functionality remains unchanged. * UI linting, formatting, and TypeScript compilation checks pass. ## Screenshots <img width="1450" height="754" alt="additional task attributes - triggerer" src="https://github.com/user-attachments/assets/20c11e5c-54e5-4e37-8f2c-584cfd93eca6"; /> Also, the screenshot in issue #67971 shows the "Dependencies Blocking Task From Getting Scheduled" section. This functionality is already present in Airflow 3. The section is displayed when a task is waiting for its upstream dependencies to complete and is hidden once the task is no longer blocked (for example, after the upstream tasks have completed). Here's the screenshot of the same: <img width="1506" height="757" alt="dependencies" src="https://github.com/user-attachments/assets/6a6469ef-6111-4a9c-a92b-87c43edc48e8"; /> Was generative AI tooling used to co-author this PR? [X] Yes Used ChatGPT to understand the codebase and assist with implementing the changes in Details.tsx. -- 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]
