Removing invalid characters from XML backups
This applies to Jira 6.4.x and above.
JIRA 3.1 and above should not suffer from this problem unless migrating to postgreSQL from another database such as MySQL. Invalid characters otherwise are automatically stripped from imported data.
In older versions of JIRA it was possible to cut & paste text containing control characters into JIRA issue fields. This causes problems, because JIRA's backup format is XML, and XML does not allow for the storage of most control characters.When XML containing control characters is imported into JIRA, the import fails with an error:
To fix this, the control characters will need to be removed from the JIRA backup file. This can be done with the following:
- Download atlassian-xml-cleaner-0.1.jar to the same folder as entities.xml
- コマンド プロンプトを開き、コンピューター上で XML または ZIP のバックアップ ファイルを見つけます。ZIP ファイル内にある場合はそれが展開されていることを確認します。この例では
entities.xmlを使います。 Run the application with the below:
java -jar atlassian-xml-cleaner-0.1.jar entities.xml > entities-clean.xmlThis will create a copy of
entities.xmlasentities-clean.xmlwith the invalid characters replaced with a replacement character �.Copy the
entities-clean.xmlfile into another directory, rename it back toentities.xmland create a new ZIP with the newly createdentities.xmlfile and theactiveobjects.xmlfile.Make sure there's no subfolders inside the zip archive, and that the files are named exacly
entities.xmlandactiveobjects.xml.Otherwise, Jira will throw an error as explained in https://confluence.atlassian.com/jirakb/unable-to-find-jira-backup-entities-xml-inside-of-zip-file-error-779160740.html- Import the new ZIP file, ensuring that it contains both XML files.
If you are seeing an error specifically with 0xffff as the affected character, please use this perl command to fix the file:
perl -i -pe 's/\xef\xbf\xbf//g' entities.xml0xfffe のエラーの場合は次の perl コマンドを使います。
perl -i -pe 's/\xef\xbf\xbe//g' entities.xmlAnd in case you are running Windows and the above Perl command doesn't work, here's a Power Shell script to fix the problem:
$yourfile = "PATH_TO_THE_XML\entities.xml"
$outputfile = "PATH_TO_SAVE_NEW_XML\entities_clean.xml"
get-content -path $yourfile | out-file $outputfile -encoding utf8The problem could be caused due to bug JRA-62240 - Getting issue details... STATUS