Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Invalid XML issue file format

Make sure you export your file in the XML format available by JIRA. Make sure you do a CTRL+S directly in your browser.

  • Do not copy and paste the date into a browser (as this would change the character encoding and potentially insert invalid characters).
  • Make sure you do not have a CSV issue file.
  • Do not manually modify the issue.xml file.
Invalid Issue Type SchemeThe selected issue type scheme for the project you just created does not match the issues in the file. For instance, you have Tasks in your xml files and Task are not present in the project issue type scheme.
Invalid JIRA instance settings

The xml file exported depends on several settings from your JIRA instance: time and date settings, time tracking, language. Make sure they are valid and compatible with XML issue file.

Trying to export from one instance and reimport to another one may cause several problems, which lead to refuse issue import.

Unicode Transformation FormatGaia for Jira app supports only UTF-8. Make sure your file has the appropriate code format.
Using Special CharactersThe XML specification defines "predefined entities" representing special characters, and requires that all XML processors honor them. These characters need to be escaped to obtain a well-formed document:
  • The < must be escaped with a &lt; entity. Since it is assumed to be the beginning of a tag.
  • The & must be escaped with a &amp; entity. Since it is assumed to be the beginning a entity reference.
  • The > should be escaped with &gt; entity. It is not mandatory and depends on the context but it is strongly advised to escape it.
  • The ' should be escaped with a &apos; entity. Mandatory in attributes defined within single quotes but it is strongly advised to always escape it.
  • The " should be escaped with a &quot; entity. Mandatory in attributes defined within double quotes but it is strongly advised to always escape it.


Look at the logs

You may investigate the reasons by looking into the atlassian-jira.log file. Go to your JIRA installation directory (chances are that it is C:\Program Files\Atlassian\Application Data\JIRA\logs and look at the last lines. You may search for "ERROR" to try to find [ca.nuum.gaia] entries. You may have a clue of what went wrong in there. 

...