Bug 1636744

Summary: Bad UI after creating a custom report
Product: Red Hat CloudForms Management Engine Reporter: Parthvi Vala <pvala>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED DUPLICATE QA Contact: Parthvi Vala <pvala>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.9.5CC: dmetzger, hkataria, jprause, lavenel, mpovolny, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.9.6   
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-11-05 16:48:16 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:
Attachments:
Description Flags
Bad UI after creating a report none

Description Parthvi Vala 2018-10-07 11:24:50 UTC 
Created attachment 1491319 [details]
Bad UI after creating a report

Description of problem:
Unnecessary `Add` and `Cancel` buttons after creating a custom report

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

How reproducible:
100%

Steps to Reproduce:
1. Navigate Cloud Intel > Reports > Reports(accordion)
2. Click on `Configuration` and select `Add a new Report`.
3. Fill in data and click on `Add` button.


Actual results:
Report is successfully created but, you see unnecessary `Add` and `Cancel` buttons.

Expected results:
`Add` and `Cancel` buttons should not appear.

Additional info:
This bug is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1624248
Comment 2 Harpreet Kataria 2018-10-08 22:11:33 UTC 
Issue was fixed in https://github.com/ManageIQ/manageiq-ui-classic/pull/4621 , After adding a schedule for a report, form buttons were still visible.

Marking PR as Gaprindashvili/yes

~Harpreet
Comment 5 Satoe Imaishi 2018-11-05 16:48:16 UTC 

*** This bug has been marked as a duplicate of bug 1624248 ***