Bug 1381728 - 'Planning options reset' flash message displayed twice
Summary: 'Planning options reset' flash message displayed twice
Keywords:
Status: CLOSED DUPLICATE of bug 1381650
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Greg Piatigorski
QA Contact: Nandini Chandra
URL:
Whiteboard: ui:optimize:planning
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 20:32 UTC by Nandini Chandra
Modified: 2016-10-11 04:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-05 19:51:11 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screen shot of Optimize->Planning page (112.70 KB, image/png)
2016-10-04 20:35 UTC, Nandini Chandra 		no flags Details
View All

Description Nandini Chandra 2016-10-04 20:32:37 UTC 
Description of problem:
----------------------
The 'Planning options reset' flash message is displayed twice on the Optimize->Planning page.


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Navigate to the Optimize->Planning page.
2.Without making any selection, click 'Reset' on the left hand panel.


Actual results:
---------------
Flash message displayed twice;Message is displayed on the left panel as well as the Planning Summary page.


Expected results:
----------------
Flash message should be displayed only once.


Additional info:
----------------
Comment 2 Nandini Chandra 2016-10-04 20:35:24 UTC 
Created attachment 1207356 [details]
Screen shot of Optimize->Planning page
Comment 3 Greg Piatigorski 2016-10-05 19:51:11 UTC 
Seems a Duplicate of this: https://bugzilla.redhat.com/show_bug.cgi?id=1381650

*** This bug has been marked as a duplicate of bug 1381650 ***
Note You need to log in before you can comment on or make changes to this bug.