cmarteepants opened a new issue, #53048:
URL: https://github.com/apache/airflow/issues/53048

   ### Body
   
   ### View
   DAG View - Tasks tab
   
   <img width="1487" height="797" alt="Image" 
src="https://github.com/user-attachments/assets/fedc037c-a69a-4a28-873b-cda6e6ab004f";
 />
   
   ### Filters to Add
   - Filter by **Operator Type**  
     ↪ Allows users to locate all tasks using specific operators (e.g., 
identify all `PythonOperator` or `EmptyOperator` tasks)
   
   - Filter by **Task Retry Count**  
     ↪ Helps highlight tasks configured with aggressive or insufficient retry 
logic
   
   - Filter by **Trigger Rule**  
     ↪ Useful when investigating DAGs with conditional task paths or debugging 
why certain tasks did not run
   
   - Filter by **Mapped Task**  
     ↪ Enables focused inspection of mapped task behaviour
   
   - Filter by **Last Instance** Date Range  
     ↪ Helps identify recently active or stale tasks, which is useful when 
investigating changes in task behaviour over time
   
   ### API Support  
   
   ❌ No
   
   - The API does not currently expose a queryable endpoint that returns task 
metadata with filtering support.
   - All task metadata is loaded client-side via DAG details and task instance 
history
   
   ### UI Impact  
   
   - Filtering could be enabled above the task list panel
   - Would significantly improve UX in DAGs with dozens or hundreds of tasks 
(e.g., dynamic DAGs or map-heavy pipelines)
   
   ### Notes  
   
   - These filters already reflect metadata displayed in the table (e.g., 
operator, trigger rule)
   - Would be particularly valuable when debugging DAGs with mapped tasks or 
unusual operator behaviour
   
   ### Committer
   
   - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow 
project.


-- 
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