Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1486555

Summary: bad breadcrumb in storage domains
Product: [oVirt] ovirt-engine Reporter: Lucie Leistnerova <lleistne>
Component: Frontend.WebAdminAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs, lsvaty, ratamir, tnisan
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:51:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
domains and volumes diff none

Description Lucie Leistnerova 2017-08-30 06:58:33 UTC
Created attachment 1319883 [details]
domains and volumes diff

Description of problem:
Normally is in breadcrumb <name of menu> >> <name of submenu as a link>. Storage domains have only 'Storage' as a link.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.2.0-0.0.master.20170828065003.git0619c76.el7.centos.noarch

How reproducible: always


Actual results: breadcrumb - Storage (link)


Expected results: breadcrumb - Storage (no link) >> Domains (link)


Additional info:
And maybe the label in Search box should be also Domains.
The same is in Administration -> Active User Sessions

Comment 1 Raz Tamir 2017-09-04 16:14:09 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos

Comment 2 Sandro Bonazzola 2017-12-20 10:51:58 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.