Bug 913084

Summary: [rhevm-reports] - RFE - Reports - Incorrect values list order for all reports with IC "Period Range"
Product: Red Hat Enterprise Virtualization Manager Reporter: David Botzer <dbotzer>
Component: ovirt-engine-reportsAssignee: Yaniv Lavi <ylavi>
Status: CLOSED ERRATA QA Contact: David Botzer <dbotzer>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, dyasny, iheim, pstehlik, Rhev-m-bugs, ykaul, yzaslavs, zdover
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.2.0Flags: dyasny: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
The order of "Period Range" values in reports containing them has been corrected.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-10 22:04:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 917401    

Description David Botzer 2013-02-20 10:37:55 UTC 
Description of problem:
The order of Period Range Values is incorrect

Version-Release number of selected component (if applicable):
3.2/sf7

How reproducible:
always

Steps to Reproduce:
1.install rhevm+report+dwh
2.create some VMs
3.Open reports with IC "Period Range" (e.x BR18)

  
Actual results:
On all reports with Period Range -
-----------
Quarterly
Yearly
Daily
Monthly

Expected results:
Should be sorted, On all reports with Period Range
e.x
Daily
Monthly
Quarterly
Yearly

Additional info:
Comment 2 David Botzer 2013-03-06 10:48:35 UTC 
Fixed, 3.2/SF9
period ranges for all reports are correct
Fixed, 3.2/SF9
Comment 3 errata-xmlrpc 2013-06-10 22:04: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.

http://rhn.redhat.com/errata/RHEA-2013-0887.html