Description
In Airflow 2 it was possible to Browse -> Task Instances and have multi-select results from search and then as "Action" run "Clear", "Clean (including downstream)", "Mark as Success", "Mark as Failed". In Airflow 3 this feature is missing and from Dag -> Task Instances menu only individual tasks can be Cleared/Marked as Success/Fail/Deleted. If you have many/multiple Task Instances, this is a very click-intensive work and no UI support is existing.
Former Airflow 2 UI:
Current UI in Airflow 3 (Missing the multi-select/Action function, individual actions on the right side):
Note that such feature exist in Admin -> Variable and Connections UI. There multi-select is implement. I would assume the approach and visual style can be transferred to the Task Instances UI
Use case/motivation
We need to have Airflow 3 closing the (last) gaps to functions that had been in Airflow 2 UI. This mass-reset/marking of Task Instances is a critical feature is you work with large scheduled run sets.
The workaround until a proper UI is available is to have a local script which aims to make this via REST API. But this is rather low-end UX.
Related issues
#60460 is related to this just for mapped tasks.
#63854 is realted to the same for Dag runs
Are you willing to submit a PR?
Code of Conduct
Description
In Airflow 2 it was possible to Browse -> Task Instances and have multi-select results from search and then as "Action" run "Clear", "Clean (including downstream)", "Mark as Success", "Mark as Failed". In Airflow 3 this feature is missing and from Dag -> Task Instances menu only individual tasks can be Cleared/Marked as Success/Fail/Deleted. If you have many/multiple Task Instances, this is a very click-intensive work and no UI support is existing.
Former Airflow 2 UI:
Current UI in Airflow 3 (Missing the multi-select/Action function, individual actions on the right side):
Note that such feature exist in Admin -> Variable and Connections UI. There multi-select is implement. I would assume the approach and visual style can be transferred to the Task Instances UI
Use case/motivation
We need to have Airflow 3 closing the (last) gaps to functions that had been in Airflow 2 UI. This mass-reset/marking of Task Instances is a critical feature is you work with large scheduled run sets.
The workaround until a proper UI is available is to have a local script which aims to make this via REST API. But this is rather low-end UX.
Related issues
#60460 is related to this just for mapped tasks.
#63854 is realted to the same for Dag runs
Are you willing to submit a PR?
Code of Conduct