-
Suggestion
-
Resolution: Unresolved
-
None
-
6
-
91
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Ensure that the JIRA export file provided by the customer is UTF-8. The encoding is specified in the XML document so it should be fairly straightforward to detect this.
Non-UTF-8 encodings aren't supported so we should stop them from getting into the system. They can't be easily converted.
Notes
If this isn't done the XML backup can fail with errors as described below:
- Unable to Restore XML Backup due to Invalid Byte Sequence for Encoding "UTF8": 0x00
- SQL Exception while Updating Issues or Importing Data in JIRA with MySQL Due to Encoding
Workaround
- is duplicated by
-
JRASERVER-41155 Have some way to filter out invalid XML characters when importing (or better yet, avoid them from being entered in the first place)
- Closed
- relates to
-
JRACLOUD-65145 Backups created from JIRA Cloud generate 'invalid XML character' and fails when imported back into Cloud.
- Closed
-
JRACLOUD-32276 When importing XML backups they should be converted into UTF-8 and have any invalid characters stripped
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- PIR - Priority Action
-
PIR-484 Loading...
- supersedes
-
JSTDEV-997 Loading...