Bug 1678192 - [RFE] BreadCrumbs should be consistent across whole CloudForms UI
Summary: [RFE] BreadCrumbs should be consistent across whole CloudForms UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.11.0
Assignee: Richard Vsiansky
QA Contact: Parthvi Vala
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-18 09:43 UTC by Loic Avenel
Modified: 2019-12-12 13:36 UTC (History)
10 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:35:55 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Cluster All (103.79 KB, image/png)
2019-05-02 15:16 UTC, Parthvi Vala
no flags Details
Cluster Summary (172.43 KB, image/png)
2019-05-02 15:17 UTC, Parthvi Vala
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:36:08 UTC

Description Loic Avenel 2019-02-18 09:43:16 UTC
BreadCrumbs should be consistent across whole CloudForms UI

Comment 4 Richard Vsiansky 2019-03-28 13:48:05 UTC
Hello,

yes. The PR was merged:

https://github.com/ManageIQ/manageiq-ui-classic/pull/4468

Comment 5 Parthvi Vala 2019-05-02 15:16:20 UTC
I tested this on 5.11.0.2.20190430174828_0e34dea, everything seemed fine, but I encountered a minor glitch.
I added 2 VMware providers and navigated to Clusters page. There were 2 clusters in total, and I navigated to one of the clusters, but I think the breadcrumb path was incorrect. Check the attachment `Cluster Summary` and see the breadcrumb path.

Need to confirm if this is missed or intended before changing the BZ status.

Comment 6 Parthvi Vala 2019-05-02 15:16:55 UTC
Created attachment 1561746 [details]
Cluster All

Comment 7 Parthvi Vala 2019-05-02 15:17:24 UTC
Created attachment 1561747 [details]
Cluster Summary

Comment 8 Parthvi Vala 2019-05-02 15:20:34 UTC
(In reply to Parthvi Vala from comment #5)
> I tested this on 5.11.0.2.20190430174828_0e34dea, everything seemed fine,
> but I encountered a minor glitch.
> I added 2 VMware providers and navigated to Clusters page. There were 2
> clusters in total, and I navigated to one of the clusters, but I think the
> breadcrumb path was incorrect. Check the attachment `Cluster Summary` and
> see the breadcrumb path.
> 
> Need to confirm if this is missed or intended before changing the BZ status.

BreadCrumb path for both the pages is same, shouldn't it be different considering how it is on other pages?

Comment 9 Richard Vsiansky 2019-05-02 15:34:12 UTC
Oh, I see where the problem is. Two controllers are using dynamic (Hosts, Clusters) titles, so the breadcrumbs need to change dynamically too. (In my version, instead of "Clusters" in the title, I see "Clusters / Deployment Roles" and everything is fine.)

The best thing to do should be opening a new BZ about this for better tracking and assigning me to it. And I am not sure what are requirements of this BZ, but because of scale of the Breadcrumbs (they are everywhere), there are, and will be, more related BZs which are handled separately.

Richard.

Comment 10 Parthvi Vala 2019-05-02 15:53:52 UTC
Agreed that this is a big change and there will be plenty of BZs coming up. I'll open a new BZ for this. Since it seems to be working fine everywhere else, changing this to Verified.


FIXED. Verified on 5.11.0.2.20190430174828_0e34dea.

Comment 13 errata-xmlrpc 2019-12-12 13:35:55 UTC
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


Note You need to log in before you can comment on or make changes to this bug.