New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-1466
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Edwin Wong [Atlassian]
Reporter: Ian Pojman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Indexing fails when invalid date custom field.

Created: 18/Mar/03 12:23 PM   Updated: 26/Nov/06 11:17 PM
Component/s: Custom Fields
Affects Version/s: None
Fix Version/s: 2.1 Pro

Time Tracking:
Not Specified

File Attachments: 1. Java Source File IssueDocument.java (9 kB)

Environment: 2.0.2

Participants: Edwin Wong [Atlassian] and Ian Pojman
Since last comment: 5 years, 22 weeks, 3 days ago
Resolution Date: 25/Mar/03 11:08 PM
Labels:


 Description  « Hide
It will blow up lucene's DateField.dateToString if an invalid date value exists in a custom field.

I had "0003-XX-XX" in one... which blew it up. I solved it by hacking IssueDocument..



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ian Pojman added a comment - 18/Mar/03 12:52 PM
of course.. you have to code the if statement correctly for that to do anything...

if (timestamp.before(DATE.getTime())) { log.error("Unable to add date custom field: date too early: "+timestamp); } else { log.error("Add date custom field: "+timestamp); doc.add(Field.Keyword(DocumentConstants.ISSUE_CUSTOMFIELD_PREFIX + customField.getLong("id"), DateField.dateToString(timestamp))); }


Edwin Wong [Atlassian] added a comment - 25/Mar/03 11:08 PM
Ian,

Thanks for the tip. The issue should be fixed in the next release.

Cheers,
Edwin