Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 978422

Summary: it is possible to set 'End Date' before 'Start Date' during report filter creation
Product: [Retired] Subscription Asset Manager Reporter: Vitaly Kuznetsov <vkuznets>
Component: SpliceAssignee: Pavlina Bartikova <pbartiko>
Status: CLOSED ERRATA QA Contact: mkovacik
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.3CC: pbartiko, whayutin
Target Milestone: rcFlags: mkovacik: automate_bug+
Target Release: 1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 11:00:42 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:
Bug Depends On:    
Bug Blocks: 833466    
Attachments:
Description Flags
sam screenshot none

Description Vitaly Kuznetsov 2013-06-26 14:53:47 UTC 
Description of problem:
It is possible to set 'End Date' before 'Start Date' during report filter creation. Surprisingly the resulting report can be non-empty.

I would suggest adding validation for filter creation (End Date >= Start Date)

Version-Release number of selected component (if applicable):
ruby193-rubygem-splice_reports-0.0.5-27.el6sam

How reproducible:
always

Steps to Reproduce:
1. During filter creation select End Date before Start Date

Actual results:
It's possible to create such filter

Expected results:
Error message displayed

Additional info:
Comment 1 wes hayutin 2013-07-17 21:42:44 UTC 
commit 7df4f7623da9f6161d6425e4ce0cb699064d7df4
Comment 2 Bryan Kearney 2013-08-02 18:52:31 UTC 
SNAP0 contains these bug fixes. Moving to ON_QA.
Comment 3 Pavlina Bartikova 2013-08-13 17:35:48 UTC 
Created attachment 786225 [details]
sam screenshot

Confirmed.

Moving bug to VERIFIED.
Comment 5 errata-xmlrpc 2013-10-01 11:00:42 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-1390.html