-
Bug
-
Resolution: Won't Fix
-
High
-
47
-
Severity 3 - Minor
-
13
-
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
Issue Summary
When trying to import the CSV file generated from the Jira service desk project, the import doesn't work successfully as the request types are not mapped correctly in the CSV file. As a result, the Customer request type field is left empty. i.e. showing the value No Match or None.
Steps to reproduce
- Export issues created in a Service Desk from JIRA to csv
- Import issues back into JIRA mapping the Customer Request Type field to the one exported by JIRA
Expected Behaviour
JIRA imports issues successfully with the expected Customer Request Type
Actual Behaviour
Issues are imported but without the Customer Request Type
The following is seen in the log
2015-01-10 12:32:08,448 JiraTaskExectionThread-5 ERROR admin 752x2267x1 55b6dr 192.168.1.173 /secure/admin/ImporterLogsPage!import.jspa [internal.customfields.origin.VpOriginManagerImpl] Invalid stored origin value Get IT help 2015-01-10 12:32:08,448 JiraTaskExectionThread-5 WARN admin 752x2267x1 55b6dr 192.168.1.173 /secure/admin/ImporterLogsPage!import.jspa [imports.importer.impl.AbstractDataImporter$1Thread[http-bio-8080-exec-5,5,main]] Cannot add value [ [Get IT help] ] to CustomField Customer Request Type in Issue null. Probably value was in incorrect format
Workaround
Replace the value in the CSV with the "correct format" value.
- Contact Atlassian Support to extract the "correct format" values from the database.
- is related to
-
JSDSERVER-1335 Can't import CSV generated from JIRA due to incorrect Customer Request Type format
- Closed
- is resolved by
-
JRACLOUD-74852 Support for Import issues from XML
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...