Created attachment 1510186 [details] Navigation via Monitor->Alerts->All Alerts Description of problem: Clicking on a provider from Monitor->Alerts->All Alerts page does lead to the provider's page. However it is slightly different from the page that it obtained by navigating to the page via Compute->Infrastructure->Providers->click on provider. Namely, the page does not display the breadcrumb of navigation. Therefore, the name of the provider is not listed anywhere on the page, which could be confusing for users (c.f. attachments). Version-Release number of selected component (if applicable): 5.10.0.25.20181120211723_d2fd659 How reproducible: 100% Steps to Reproduce: 1. Configure an appliance with a provider (e.g. infra) 2. Setup an alert to fire against that provider 3. Navigate to Monitor->Alerts->All Alerts 4. Click on the providers name in the list-view of the provider Actual results: There is no breadcrumb and no indication of what provider you are looking at on the page. Expected results: The page should display the breadcrumb so that the user knows what provider they are looking at. Additional info: The vertical navigation panes display that the correct items have been selected in either case (e.g. Compute->Infrastructure->Providers).
Created attachment 1510187 [details] Navigation via Compute->Infrastructure->Providers
https://bugzilla.redhat.com/show_bug.cgi?id=1655114
https://github.com/ManageIQ/manageiq-ui-classic/pull/5148
Verified in 5.11.0.1.20190424210327_58b5dbd Steps of verification: 1. Configure an appliance with a provider (e.g. infra) 2. Setup an alert to fire against that provider 3. Navigate to Monitor->Alerts->All Alerts 4. Click on the providers name in the list-view of the provider 5. Verified that the breadcrumb is present, which lists the correct provider.
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