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

Button role-based visibility rules do not work in UI Service #1907

Open
eggoide opened this issue Jun 14, 2024 · 3 comments
Open

Button role-based visibility rules do not work in UI Service #1907

eggoide opened this issue Jun 14, 2024 · 3 comments
Assignees

Comments

@eggoide
Copy link

eggoide commented Jun 14, 2024

Hi, I would like to report the following bug:
We are running Manage IQ petrosian-1.20230912222549_a07cb46 in a docker container. However, we have experienced this behaviour even before in version Najdorf.

The thing is that when I create a button and set its visibility to one role, it works in classic UI but it is completely ignored in /ui/service

How to reporoduce:

  1. I have created user1 and user2
  2. Created groups user1_group and user2_group
  3. Created user1_role and user2_role and assigned them accordingly to the user and group

image

  1. I have created a test button and set the visibility to user1_role
    image

Now, user1 should see the button and user2 should not.
In classical UI it works:
user1:
image

user2:
image

However in UI Service, the button is shown to both users nevermind the visibility settings.
user1:
image

user2:
image

@eggoide eggoide added the bug label Jun 14, 2024
@Fryguy
Copy link
Member

Fryguy commented Jun 19, 2024

@GilbertCherrie Can you please take a look at this one?

@GilbertCherrie
Copy link
Member

Yeah I can take a look.

@miq-bot miq-bot added the stale label Sep 23, 2024
@miq-bot
Copy link
Member

miq-bot commented Sep 23, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants