-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global permissions on UI are in a random order #11010
Comments
I see a slightly different order in 2.9-head that is probably the same issue and should be fixed
The UI (shell/components/GlobalRoleBindings.vue) hasn't changes in a number of years, and it doesn't look like sorting was ever done on global non-builtin / non-custom roles. I suspect the order in which we receive them has changed. We should ensure the order is correct in the UI though |
/forwardport v2.9.0 |
/forwardport v2.8.next1 |
For docs (cc: @btat) we need a release note for the current 2.7.next1 (2.7.13) as we move this work to a later version. It is a regression though the UI around this hasn't changed in years so we'll have to look at the data given to us. |
Will not fix for 2.7.x. We have tickets for 2.9.x & 2.8.x at this stage though based on timing, we have to sort this out in 2.9.x first (or even 2.10.0 now) |
Setup
release-2.7 d14964b0d
Describe the bug
Global permissions on the Users and authentication page, have the permissions in a different order.
To Reproduce
Result
Expected Result
Expected the order to be:
Screenshots
![2024-05-10_16-43-26](https://private-user-images.githubusercontent.com/38144301/329738774-6293e3d3-7187-4c85-a09f-8e708cad2e53.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4Njk3MjYsIm5iZiI6MTczODg2OTQyNiwicGF0aCI6Ii8zODE0NDMwMS8zMjk3Mzg3NzQtNjI5M2UzZDMtNzE4Ny00Yzg1LWEwOWYtOGU3MDhjYWQyZTUzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDE5MTcwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWIxMWU3MGRkOGIxZjBiYzQ1MzMzMGJmYTc0Y2NlMzBiYTZkYjA4MjcwYzEzYWE0NGUxMTRkNGVhMWU5MjhmOGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.8dOrRTgyUzrvctNoS1mGMQwhMjRQnU7fwzKyhIAK-GE)
Additional context:
Do not see the issue on v2.7.12
The text was updated successfully, but these errors were encountered: