Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a bug
Priority: Low
Fix Version/s: None
Affects Version/s: 3.10.2, 5.1.3
Component/s: Issue - Fields
Labels:

Introduced in Version:
3.1
Bug Fix Policy:
View Atlassian Server bug fix policy

Currently, some users are entering the due date invalidly as "01/Aug/7", this will be stored as "01/Aug/0007" in the database.

The same string entered in a custom field date will result in an error: "Date too early. Dates must be after 1970".

We should prevent users entering invalid dates like this by reusing the custom field date validation code's checks in our built-in date fields (eg. due date, version release dates, worklog dates).

relates to

JRASERVER-10246 entry of date 0.jul.06 doesnt result in error

Closed

JRASERVER-9141 Able to enter invalid date in Due Date field (Create new issue)

Closed

JRASERVER-20007 Default date format is two-digit and loses century chosen in calendar picker

Gathering Impact

JRASERVER-1375 Mandatory fields (aka custom validation)

Gathering Interest

Assignee:: Unassigned

Reporter:: Zhen Yueh, Lean [Atlassian]

Votes:: 3 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: 23/Aug/2007 7:12 AM

Updated:: 27/Mar/2019 11:52 PM

Resolved:: 23/Mar/2015 5:26 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates