Summary

When JIRA Portfolio creates a plan export, it produces a UTF-8 encoded file. This is the expected behaviour. Subsequently importing this file uses the System File Encoding. This introduces a problem with some characters in various encodings as the characters become corrupt.

Environment

JIRA 6.4.12,
JIRA Portfolio 1.10.4

Steps to Reproduce

1. Set a JIRA environment up to use: -Dfile.encoding=cp1252" encoding.
2. Create a Plan which includes characters which vary in encoding.
3. Export this plan.
4. Confirm the plan opens as a UTF-8 Encoded file using a text editor.
5. Import the plan.
6. Observe the characters become corrupt. JIRA Portfolio has treated the file as a 'cp1252 encoded file.

Expected Results

JIRA Portfolio should treat the file as a UTF-8 file on import and export.

Actual Results

JIRA Portfolio corrupts some characters, when the system file encoding is not UTF-8.
For Example:

这是一个例子

Becomes:

这是一个例子

Workaround

Set the File Encoding to UTF-8 in JIRA.
This can be done by adding the property -Dfile.encoding=utf-8": by following the instructions in: Setting Properties and options on startup.

Note: This will not fix existing corrupted plan templates, that have been previously imported/exported and contain corrupted characters when accessed with a text editor using UTF-8 encoding.