Bug 1486555 - bad breadcrumb in storage domains
Summary: bad breadcrumb in storage domains
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Tal Nisan
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-30 06:58 UTC by Lucie Leistnerova
Modified: 2017-12-20 10:51 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:51:58 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)
domains and volumes diff (8.63 KB, image/png)
2017-08-30 06:58 UTC, Lucie Leistnerova 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81203 0 master MERGED webadmin: Change storage domains breadcrumb to 'Storage Domains' 2017-08-30 12:24:10 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.