I am trying to import a companies trac project into jira. Currently I have a problem when importing issues containing special german chars. It seems that all umlauts occurring in the trac ticket description are not correctly recognized. After the import they show up as questionmarks (?).
I made sure that all 'layers' and components are configured to us utf8:
Actually it somehow works: Umlauts used in the trac ticket summary are correctly handled during import. No problem here. Also when creating new issues in jira: no problem here ! Importing issues with umlauts using csv importer works as well. No problems with umlauts here !
I checked the postgres db: The questionmarks occur already in the jiraissue table (column description). I noticed that the type postgres db type is VARCHAR rsp. TEXT for column summary rsp. description. However, I dont believe that this matters.
Any ideas ?
|Indexing language||English - Aggressive Stemming|
|Installed languages||English (UK)|
English (United States)
|Default language||English (United States)|
|Default user time zone||(GMT-06:00) GMT-6|
some more settings:
|Java Vendor||Oracle Corporation|
|JVM Vendor||Oracle Corporation|
|JVM Implementation Version||21.0-b17|
|Java Runtime||Java(TM) SE Runtime Environment|
|Java VM||Java HotSpot(TM) 64-Bit Server VM|
|User Locale||English (United States)|
|Operating System||Linux 3.13.0-77-generic|
|Application Server Container||Apache Tomcat/7.0.55|
|Database JNDI address||postgres72 jdbc:postgresql://172.17.0.3:5432/postgres|
|Database driver||PostgreSQL Native Driver PostgreSQL 9.0 JDBC4 (build 801)|
|Build Date||Tue Feb 03 00:00:00 CET 2015|
The cause of this problem is the difference between the encoding in the Excel file and CSV. The following steps shows how to solve it:
I should have mentioned, that I am using the "Trac Importer" (https://confluence.atlassian.com/jira/importing-data-from-trac-238617182.html). Hence there is no csv or excel data. I directly import the zipped trac.db and other files, as described in the reference.
Regarding csv imports in general: I tried to import a test csv file and found there is no problem with character encoding. However, currently I think using csv import method is no good option when importing the entire project from trac with thousands of issues.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot