Bug 978422 - it is possible to set 'End Date' before 'Start Date' during report filter creation
Summary: it is possible to set 'End Date' before 'Start Date' during report filter cre...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: Splice
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 1.3
Assignee: Pavlina Bartikova
QA Contact: mkovacik
URL:
Whiteboard:
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
 
Reported: 2013-06-26 14:53 UTC by Vitaly Kuznetsov
Modified: 2013-10-01 11:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 11:00:42 UTC
Embargoed:
mkovacik: automate_bug+

Attachments (Terms of Use)
sam screenshot (70.01 KB, image/png)
2013-08-13 17:35 UTC, Pavlina Bartikova 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1390 0 normal SHIPPED_LIVE Release 1.3 of Subscription Asset Manager 2013-10-01 14:43:14 UTC

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
Note You need to log in before you can comment on or make changes to this bug.