Skip to content
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

Closed
anupama2501 opened this issue May 11, 2024 · 6 comments
Closed

Global permissions on UI are in a random order #11010

anupama2501 opened this issue May 11, 2024 · 6 comments
Labels
area/user kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this release-note status/release-note-added status/wontfix
Milestone

Comments

@anupama2501
Copy link

Setup

  • Rancher version: v2.7.13-rc4
  • Rancher UI Extensions: release-2.7 d14964b0d
  • Browser type & version: Chrome

Describe the bug
Global permissions on the Users and authentication page, have the permissions in a different order.

To Reproduce

  1. Install rancher 2.7.13-rc4
  2. Navigate to users and authentication >> Users
  3. Create a user
  4. Notice the order of the global permissions

Result

Restricted Admin
User base
Administrator
Standard user

Expected Result
Expected the order to be:

Administrator
Restricted Admin
Standard user
User base

Screenshots
2024-05-10_16-43-26

Additional context:
Do not see the issue on v2.7.12

@anupama2501 anupama2501 added this to the v2.7.next1 milestone May 11, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label May 11, 2024
@richard-cox
Copy link
Member

richard-cox commented May 13, 2024

I see a slightly different order in 2.9-head that is probably the same issue and should be fixed

  1. Admin
  2. User-Base
  3. Restricted Administrator
  4. Standard User

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

@richard-cox
Copy link
Member

/forwardport v2.9.0

@richard-cox
Copy link
Member

/forwardport v2.8.next1

@gaktive
Copy link
Member

gaktive commented May 13, 2024

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.

@gaktive gaktive modified the milestones: v2.7.next1, v2.7.next2 May 13, 2024
@btat
Copy link

btat commented May 13, 2024

cc @LucasSaintarbor

@gaktive
Copy link
Member

gaktive commented Jun 19, 2024

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/user kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this release-note status/release-note-added status/wontfix
Projects
None yet
Development

No branches or pull requests

5 participants