Bug 1535928

Summary: [RFE] Back options on datastore page doesn't have option to navigate to all page of datastore
Product: Red Hat CloudForms Management Engine Reporter: Anurag <ansinha>
Component: UI - OPSAssignee: Richard Vsiansky <rvsiansk>
Status: CLOSED ERRATA QA Contact: Parthvi Vala <pvala>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: akarol, cpelland, dmetzger, hkataria, lavenel, mpovolny, obarenbo, ohadlevy, pvala, simaishi
Target Milestone: GAKeywords: FutureFeature
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: :ui:datastore
Fixed In Version: 5.11.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:33:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Anurag 2018-01-18 09:36:58 UTC
Created attachment 1382802 [details]
Screenshot

Description of problem:
When we go to detail page of datastore, back button doesn't have the option to navigate to datastore all page.


Version-Release number of selected component (if applicable):
Version 5.9.0.17.20180116225234_ac8b6f5 


How reproducible:
100%


Steps to Reproduce:
1.Add a infraprovider on CFME appliance
2.Navigate to Compute-->Infrastructure-->Datastore
3.Select a datastore
4.Click on the back icon(upper left)


Actual results:
No option to navigate to all page (page that has all the datastore listed)

Expected results:
There should be a option to navigate to all page.


Additional info:

Comment 7 Richard Vsiansky 2019-03-25 08:27:54 UTC
https://github.com/ManageIQ/manageiq-ui-classic/pull/4468

Comment 8 Parthvi Vala 2019-05-02 15:26:06 UTC
FIXED. Verified on 5.11.0.2.20190430174828_0e34dea.

Comment 10 errata-xmlrpc 2019-12-12 13:33:48 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