Bug 1472411

Summary:	Unexpected Accordions behavior on non-explorer summary screens.
Product:	Red Hat CloudForms Management Engine	Reporter:	Harpreet Kataria <hkataria>
Component:	UI - OPS	Assignee:	Dávid Halász <dhalasz>
Status:	CLOSED CANTFIX	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.8.0	CC:	dajohnso, dhalasz, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Keywords:	FutureFeature
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-06 12:00:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:
Embargoed:

Description Harpreet Kataria 2017-07-18 16:23:49 UTC

Description of problem: Unexpected Accordions behavior on non-explorer summary screens.


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


How reproducible: 100%


Steps to Reproduce:
1. Go to Compute/Infrastructure/Providers lists
2. Select a Provider
3. On provider summary screen, click on any relationship link from listnav, after link is clicked, accordion in the listnav collapses, it should remain opened.
4. Next, expand an accordion in listnav, then navigate away from Compute/Infrastructure/Providers area, then navigate back to Compute maintab, previously opened/expanded accordion in listnav is no longer expanded, it should remain expanded.

Actual results: open state of accordion in listnav on non-explorer screens is not being remembered when clicking on relationships links or when returning back to the screen from another screen


Expected results: Opened state of accordion should be remembered.


Additional info:

Comment 4 Dave Johnson 2018-01-16 01:57:06 UTC

Removing Regression and Blocker flag after David reached out and explained that this functionality has never existed for non-explorer pages.  This is the way its been forever, the logic just doesn't exist.  We haven't had a customer hit this but its still inconsistent behaviour in the UI, bumping priority to high.