devgonvarun opened a new issue, #53936: URL: https://github.com/apache/airflow/issues/53936
### Apache Airflow version 3.0.3 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? Case: Custom airflow role with access to some dags. The "Runs" and "Task Instances" submenus in the "Dags" Menu only work with "Can Read on Dags" permission which gives permission to read on all dags not just some dags. For example: when only using "can read on DAG:dag1" permission for example, the "Runs" and "Task Instances" submenus have a 403 error. <img width="976" height="1200" alt="Image" src="https://github.com/user-attachments/assets/de17827f-d674-465b-acdd-9eaa438f13c9"; /> "can read on Task Instances", "menu access on Task Instances", "can read on DAG Runs", "menu access on DAG Runs" work fine when going through a selected dag. <img width="1210" height="535" alt="Image" src="https://github.com/user-attachments/assets/07aa9e1a-ddb0-4eae-a44b-cef75aa27fcc"; /> ### What you think should happen instead? "Runs" and "Task Instances" should list the runs and task instances for the dags the logged in user's roles have access for. ### How to reproduce Create a new airflow user with access to only some dags: remove "can read on DAGs" permission and instead add "can read on DAG:X" permission where dag_id=X for your newly created role. Then using this new role, navigate to the "Runs" and "Task Instances" submenus in the "Dags" Menu screen as shown in the screenshots above. ### Operating System Debian GNU/Linux 12 (bookworm) ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details Helm Chart v 1.18.0 ### 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]
