-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
4.0.1
-
JIRA 4.0.2 (also reproduces in 4.0.1 and 4.1 trunk)
-
4
-
2
-
Severity 2 - Major
-
0
-
The issue creation / editing UI allows the entry of invalid dates, which then cause errors when JIRA attempts to display them.
1) Create a new issue.
2) Set the Due Date to "14/Jan/65536" and save the issue.
3) Search for the issue in the Issue Navigator.
A velocity error is displayed instead of the search results:
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.issue.fields.layout.column.ColumnLayoutItemImpl threw exception class com.atlassian.jira.util.LuceneUtils$DateParsingException : Input is not valid date string: 655360113130000 at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:249) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at ...
Consequently, unless the ID for the incorrect issue is known, the users cannot find the issue again to remove the invalid data.
4) Navigate to the Dashboard and look at the Activity Stream gadget.
It displays an error box which links to a System Error page:
Error occured getting activity: Input is not valid date string: 655360113130000 Referer URL: http://localhost:8080/plugins/servlet/gadgets/ifr?container=atlassian&mid=10001&country=AU =en&view=default&view-params=%7B%22writable%22%3A%22false %22%7Dt=atlassian%3AXtfQK%2BvfYaDh8uHzTkXYLQ%2BUIsau8PzjWEvOVjBsLsEmvNj8lo6d4x2GL DqHyloyEOnz2NSY1%2Bv9o5fLVt3NUH5VCYWV6NVBEu%2FMHGC8b7icyc2dwg86LEL5OgEOcq%2FBLBAjMlmPeqhO kHaE7Xlh8b2SC%2FUT5v7afZPIGanv1PxpqKne5OAFqiAzRHt6WJAs9X7N7YVa85lBqaIZNGNuzxjfbVkLVSc4BYij LcTGWgr5DAB5uHmuvXDhOoCMXamtJXOJqTgzWTKjSCsfWWduQUqOQGf2RbuF%2BVy8RpiuU%2Bnp15n97y92G7FQKF e7mdrNZSxisw%3D%3D&up_isConfigured=true&up_isConfigurable=true&up_refresh=false&up_title= Your+Company+JIRA&up_titleRequired=true&up_keys=__all_projects__&up_itemKeys=&up_username= &up_numofentries=5&url=http%3A%2F%2Flocalhost%3A8080%2Frest%2Fgadgets%2F1.0%2Fg%2F com.atlassian.streams.streams-jira-plugin%3Aactivitystream-gadget%2F gadgets%2Factivitystream-gadget.xml
- is duplicated by
-
JRASERVER-21746 Insane but technically valid values in the datevalue field of the customfieldvalue table
- Closed
- relates to
-
JRASERVER-21366 Cannot index Customfield Datepicker with date < 1970
- Gathering Impact