Description of problem: Button group is shown in self-service portal even when no buttons or rights are assigned. Version-Release number of selected component (if applicable): Version 5.9.2.4.20180501195858_35dc609 How reproducible: 100% Steps to Reproduce: Create one button group with one button. - Navigate to Automation -> Automate -> Customization -> Buttons -> Configuration -> Add a new button group under VM and instance. - Create a button with Visibility Expression "VM and Instance.My Company Tags : Department CONTAINS 'Marketing'". - Set the button visibility to all. Refer - button.png Actual results: In the Operational portal, the button group is not shown in VM and Instances. In self UI, the button group is visible in VM and Instances. Expected results: It should not be shown when visibility expression does not match.
Created attachment 1450866 [details] button description
I took a look this ticket and believe it should be assigned over to API team because Service UI doesn't do any work to figure out what should be displayed when data comes back from the API. If the API returns it, service UI will render it. Let me know if you would like me to help test this later after they have made a change to ensure the API doesn't return this information.
https://github.com/ManageIQ/manageiq/pull/17607
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/739171cd17e362306a58f275de0489e90d9dab36 commit 739171cd17e362306a58f275de0489e90d9dab36 Author: Dávid Halász <dhalasz> AuthorDate: Tue Jun 19 07:10:50 2018 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Tue Jun 19 07:10:50 2018 -0400 Reject empty button groups from the result of #custom_actions Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1590764 app/models/mixins/custom_actions_mixin.rb | 2 +- spec/models/mixins/custom_actions_mixin_spec.rb | 31 + 2 files changed, 32 insertions(+), 1 deletion(-)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212