Bug 1026127 - [ALL_lang] Future date can be selected
Summary: [ALL_lang] Future date can be selected
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 4.0
Hardware: Unspecified
OS: All
low
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Julie Pichon
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-04 01:09 UTC by Mie Yamamoto
Modified: 2015-02-15 22:02 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:23:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Future date can be selected (176.09 KB, image/png)
2013-11-04 01:09 UTC, Mie Yamamoto
no flags Details

Description Mie Yamamoto 2013-11-04 01:09:53 UTC
Created attachment 818858 [details]
Future date can be selected

Description of problem:
If the start date selected is in the past, you can select future date in the end date field without errors.


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


How reproducible: 100%


Steps to Reproduce:
1.. Click on Admin-System Panel-Overview tab from the left side panel, 
2. Select the date in the past in the start date field.
3. Select the date in the future in the end date field

Actual results:
No error


Expected results:
Error should be displayed  (you selected a future date etc)


Additional info:

Comment 2 Julie Pichon 2013-11-12 14:59:18 UTC
Could you explain why this is a problem, or why it is confusing? As far as I can tell, if selecting a date far into the future, there won't be any data to display therefore there shouldn't be any problem.

We could add a javascript check to prevent it, but I wonder if it's actually necessary - for instance if some machines are generating data in a timezone far away you could reasonably have data labelled for what is "tomorrow" for you.

Comment 3 Julie Pichon 2014-01-21 16:23:39 UTC
Closing per comment 2.


Note You need to log in before you can comment on or make changes to this bug.