Created attachment 1492791 [details] Custom patch created by the customer * Description of problem: When used with Service Now Portal, CFME is communicating over API with IDs of VMs, Reports, Report results, etc. When something is needed to be troubleshooted, or checked, the user needs also to go to the API and drill for the names. This makes troubleshooting efforts difficult and slow. The customer has prepared a custom patch which will display item IDs in CFME GUI and would like to push it to the upstream. There is no bandwidth in customers organization to take care of the process but because they become TAM customer recently, we would like to do the extra step for them. Can someone please take the ownership of this patch and push it to the upstream? * Version-Release number of selected component (if applicable): Red Hat CloudForms 4.6 * How reproducible: Always * Actual results: No item IDs visible in the GUI. * Expected results: Item IDs visible in the GUI.
https://github.com/ManageIQ/manageiq-ui-classic/pull/5342
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/c387a0e0dc924fd218f734bc4d4c668d8c524b84 commit c387a0e0dc924fd218f734bc4d4c668d8c524b84 Author: Harpreet Kataria <hkataria> AuthorDate: Thu Mar 14 15:30:29 2019 -0400 Commit: Harpreet Kataria <hkataria> CommitDate: Thu Mar 14 15:30:29 2019 -0400 Fixed search condition to be an OR condition - Changing condition to be an OR condition to address https://github.com/ManageIQ/manageiq-ui-classic/pull/4791/files#r236382928 - Fixed indentation of ID column of role details screen. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1638245 app/controllers/application_controller.rb | 29 +- app/views/ops/_rbac_role_details.html.haml | 2 +- 2 files changed, 19 insertions(+), 12 deletions(-)
Verified in 5.11.0.11
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/RHBA-2019:4199