yuseok89 opened a new pull request, #69619:
URL: https://github.com/apache/airflow/pull/69619
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
closes: #66947
Each Dag card and table row on the Dag list page now shows the task-instance
state breakdown of that Dag's most recent run, as clickable badges. Clicking a
badge opens that run's task list filtered by the state — restoring the "Recent
Tasks" scan → click workflow from Airflow 2.
### What changed
- **New endpoint** `GET
/api/v2/ui/dags/latest_run_task_instance_state_counts`: for the requested Dag
IDs it resolves each Dag's latest run and counts its task instances grouped by
state. `dag_ids` is bounded to the API max page limit, and rows read per run
are capped.
- **Card view**: state badges below the recent-runs bar chart.
- **Table view**: compact badges in a new "Latest run tasks" column.
- **Dynamic badges**: only states present in the run are shown, ordered by
priority; task instances with no state yet appear as `no_status`.
Unlike the run-state badges from #67242 (which count how many of a Dag's
runs are in each state), these count the task instances of its single latest
run.
### Demo
https://github.com/user-attachments/assets/6d1fa80e-12a7-4438-8580-2a05a72c434b
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [x] Yes (please specify the tool below)
- Opus 4.8
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
