It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hello,
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 ?
Internationalization settings:
Indexing language | English - Aggressive Stemming |
Installed languages | English (UK) English (United States) French (France) German (Germany) Japanese (Japan) Spanish (Spain) |
Default language | English (United States) |
Default user time zone | (GMT-06:00) GMT-6 |
some more settings:
Java Version | 1.7.0 |
Java Vendor | Oracle Corporation |
JVM Version | 1.7 |
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 Name | jira |
User Timezone | Europe/Berlin |
User Locale | English (United States) |
System Encoding | ANSI_X3.4-1968 |
Operating System | Linux 3.13.0-77-generic |
OS Architecture | amd64 |
Application Server Container | Apache Tomcat/7.0.55 |
Database type | postgres72 |
Database JNDI address | postgres72 jdbc:postgresql://172.17.0.3:5432/postgres |
Database URL | jdbc:postgresql://172.17.0.3:5432/postgres |
Database version | 9.4.0 |
Database driver | PostgreSQL Native Driver PostgreSQL 9.0 JDBC4 (build 801) |
JIRA info:
Version | 6.3.15 |
Build Number | 6346 |
Build Date | Tue Feb 03 00:00:00 CET 2015 |
Build Revision | dbc023dd75cecacf443c4b235f66124b15f5c5fe |
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:
Hello Moe,
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.