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

   ### Apache Airflow version
   
   3.1.5
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   While testing PR https://github.com/apache/airflow/pull/60015 for fixing Fab 
user management screens I noticed one further glitches in UI workflow:
   
   1) If you have a user created and you edit the user via the UI
   <img width="551" height="159" alt="Image" 
src="https://github.com/user-attachments/assets/7dec9274-f956-4969-8792-a109183cc64f";
 />
   ...then on the screen where the user can be edited a "Groups" selection is 
displayed:
   <img width="1048" height="316" alt="Image" 
src="https://github.com/user-attachments/assets/5eeedf12-ec09-4827-a6ca-c1b4941a24ee";
 />
   ...whereas Airflow does not use Groups and does not have them. There are 
also no Groups selectable. The UI element needs to be hidden
   
   ### What you think should happen instead?
   
   Edit UI should be consistent
   
   ### How to reproduce
   
   Start Airflow on main and follow the steps described via `breeze 
start-airflow --python 3.12 --load-example-dags --backend postgres --executor 
LocalExecutor --auth-manager FabAuthManager`
   
   ### Operating System
   
   Linux
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   breeze
   
   ### 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