josh-fell opened a new issue, #49405:
URL: https://github.com/apache/airflow/issues/49405

   ### Apache Airflow version
   
   3.0.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   In the Airflow UI, Task Group "instances" are not selectable -- applicable 
for both the grid and graph views. This means that users can no longer 
clear/update the state of individual Task Groups. In previous versions this was 
possible. Unfortunately this means fine-tuned control of Task Group state needs 
to handled by updating state of each task within the Task Group.
   
   
https://github.com/user-attachments/assets/6ce0c457-b15a-472a-b689-ba0ea996ba3f
   
   ### What you think should happen instead?
   
   Users should be allowed to update the state of individual Task Groups in the 
Airflow UI like with pre-Airflow 3 versions.
   
   ### How to reproduce
   
   - Create a pipeline with Task Groups and trigger a DAG run
   - Attempt to select an individual Task Group in either the grid or graph view
   
   Toy DAG if needed:
   ```py
   from airflow.decorators import dag, task_group
   from airflow.operators.empty import EmptyOperator
   from airflow.sdk.bases.operator import chain
   
   
   @dag
   def tg():
       @task_group
       def group():
           chain(*[EmptyOperator(task_id=i) for i in "abcdefg"])
   
       group()
   
   tg()
   ```
   
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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