-
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 #11013
Comments
@richard-cox I have brought up a fresh 2.9 and the permissions order seems correct to me: |
It looks like we rely on the order provided in the API response to glovalroles. Sometimes this is correct, sometimes not |
So should we sort them alphabetically, or hard code an order for the ones we want in that order and show any others below? |
Would vote we hard code the order, but still only show the ones the user can see (aka exist in the globalroles response). Not sure they'll ever not be able to see them all but just in case |
Assigning to @rak-phillip in case that PR does tackle this ticket, which could then move to Working or later. |
@gaktive I think this issue number inadvertently got pulled in with the forward porting effort for user retention. Removing the link from the PR. |
e2e test is sufficient! moving to done |
This is a forwardport issue for #11010, automatically created via GitHub Actions workflow initiated by @richard-cox
Original issue body:
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.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4NjAzOTAsIm5iZiI6MTczODg2MDA5MCwicGF0aCI6Ii8zODE0NDMwMS8zMjk3Mzg3NzQtNjI5M2UzZDMtNzE4Ny00Yzg1LWEwOWYtOGU3MDhjYWQyZTUzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDE2NDEzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJkNzEyNDM0YWE0NzliZGFhOTExNzhjMWM2NzRiYTI0Yzk5NTZiOGE3ZmZjODkwZWY3Y2JiZDg4MmIzNDYwNTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.V5ao0wylbN1ZxQlHVCrWCZOialQA8L-jlwnSe8bgpgE)
Additional context:
Do not see the issue on v2.7.12
The text was updated successfully, but these errors were encountered: