New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-8480
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Anton Mazkovoi [Atlassian]
Reporter: Anton Mazkovoi [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Invalid change items generated after doing an XML export and re-import for text fields

Created: 10/Nov/05 05:43 PM   Updated: 04/Jan/07 12:14 AM
Component/s: Import / Export
Affects Version/s: None
Fix Version/s: 3.4.1

Time Tracking:
Not Specified

Participants: Anton Mazkovoi [Atlassian]
Since last comment: 2 years, 41 weeks, 5 days ago
Resolution Date: 10/Nov/05 05:58 PM
Labels:


 Description  « Hide
The problem is that most web browsers submit multi-line contents of text areas teminated by \r\n characters (windows line terminators). These get exported properly to XML on backup. The problem is that according to XML spec upon parsing the XML file the line terminators are normalised to \n:
http://www.xml.com/axml/target.html#sec-line-ends

This means that next time an issue is edited the values appear different as the \r characters do not exists in the database but are sent by the web browser.

This problem surfaces when one exports JIRA data to XML and then reimports the data.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] added a comment - 10/Nov/05 05:58 PM
Now field values for text fields (Custom Text Fields, Environment and Description) are compared by normalising line feeds first. This also fixes problems with browsers that do not send Text Area contents terminated by \r\n, but only with \n. For example Konqueror.