Bug 1336923

Summary: Unable to get to filter tab while editing Chargeback reports
Product: Red Hat CloudForms Management Engine Reporter: Nandini Chandra <nachandr>
Component: ReportingAssignee: Libor Pichler <lpichler>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: jhardy, lpichler, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: report:chargeback
Fixed In Version: 5.6.0.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 16:03:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nandini Chandra 2016-05-17 19:54:25 UTC 
Description of problem:
-----------------------


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


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


Steps to Reproduce:
------------------
1.Create a Chargeback report.
2.Edit the report.
3.Clicking on the filter tab doesn't take you to the filter tab.


Actual results:
--------------
It's not possible to get to the filter tab while editing Chargeback reports.


Expected results:
-----------------
It should be possible to get to the filter tab while editing Chargeback reports.


Additional info:
----------------
Comment 2 Libor Pichler 2016-05-18 09:01:29 UTC 
https://github.com/ManageIQ/manageiq/pull/8655
https://github.com/ManageIQ/manageiq/pull/8559
Comment 3 Nandini Chandra 2016-05-26 15:33:03 UTC 
Verified in 5.6.0.8
Comment 5 errata-xmlrpc 2016-06-29 16:03:19 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-2016:1348