Description of problem: Custom buttons show for objects like vm or instance but may be for functionality that would only apply to a provider or service. A filter mechanism is needed. Version-Release number of selected component (if applicable): How reproducible: N/A, RFE Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Ability to set filtering criteria in both Admin & Ops UI and the SelfServe UI for buttons. The examples are for VM/Instance but thought needs to go into actions applicable at all of the places that custom buttons can be attached. Additional info: Currently if there are multiple types of actions created in buttons the pattern has been to create a button group that describes the functions under that group i.e "VMware actions", "AWS Actions"
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-2018:0380