[#JRA-6822] Inconsistent Locales used when importing date custom field through CSV

JIRA

Inconsistent Locales used when importing date custom field through CSV

Created: 30/May/05 08:04 PM Updated: 30/Jul/06 07:37 PM

Component/s:

Import / Export

Affects Version/s:

3.2 Beta

Fix Version/s:

3.2.1

Time Tracking:

Not Specified

Participants:	Brian Nguyen [OLD]
Since last comment:	3 years, 26 weeks, 6 days ago
Resolution Date:	31/May/05 12:57 AM
Labels:

Description

« Hide

The CSV Importer currently uses the Default Locale to map strings into dates. But then uses the User Locale to import the date into the issue.
It causes this error
com.atlassian.jira.issue.customfields.impl.CustomFieldValidationException: Invalid date format. Expected d-MMM-yy
> at com.atlassian.jira.issue.customfields.converters.DatePickerConverter.getTimestamp(DatePickerConverter.java:40)
> at com.atlassian.jira.issue.customfields.impl.DateCFType.getSingularObjectFromString(DateCFType.java:45)
> at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:428)
> at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:86)
> at com.atlassian.jira.imports.importer.impl.ImporterThread.run(ImporterThread.java:16)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brian Nguyen [OLD] added a comment - 30/May/05 11:49 PM

There is also a problem with the Importer Thread in that it doesn't specify a user and returns the JIRA Default Locale while the mapper uses the JVM Locale

[ Permlink | « Hide ]

Brian Nguyen [OLD] added a comment - 31/May/05 12:57 AM

The csv importer will now always use the User's Locale to translate