Bug 1475248 - Back button disable while navigating instance from provider itself
Summary: Back button disable while navigating instance from provider itself
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: User Experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: cfme-future
Assignee: Serena
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-26 09:31 UTC by Nikhil Dhandre
Modified: 2019-08-06 20:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-12 14:21:37 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nikhil Dhandre 2017-07-26 09:31:04 UTC
Description of problem:

Back button disables when freshly navigate to an instance using the provider.
(compute > clouds > providers > Azure > Instance) 


How reproducible: always


Steps to Reproduce:

Method-1
1. add cloud appliance Azure
2. compute > clouds > providers > Azure > 
                          In Relationships > Instances > Select any one Instance.
3. You will get >>>>> back button disable. 

Method-2:
1. close appliance UI and log in again.
2. compute > clouds > Instances > select last Instance.
3. You will get >>>>> back button enables with history(All instances by provider) for navigation.


Actual results:
Back button disable

Expected results:
Back button enable

I think in the first method also its has to enable with history(All instances by provider)

Additional info:
Yes, In explorer in both method "Instances by Provider" tab is there. but still....

Snapshots:

M-1: https://drive.google.com/a/redhat.com/file/d/0BwdZUxbvLToZZDB6dml1Q3lTdGc/view?usp=sharing

M-2: https://drive.google.com/a/redhat.com/file/d/0BwdZUxbvLToZV19od3kxRU5fNmM/view?usp=sharing


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