Uploaded image for project: 'JIRA Importers Plugin'
  1. JIRA Importers Plugin
  2. JIM-596

Backslash in now a special character in CSV (JIM and JIRA specific)

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • Icon: Medium Medium
    • None
    • None
    • CSV
    • None

      Due to changes in CSV parser a backslash became a special character.

      If the backslash is found inside of quoted text it will be ignored (removed) unless it precedes another backslash or a double quote. In case it does the following character will be kept but the first backslash will be omitted.

      Both JIM and JIRA are affected. Probably worth mentioning somewhere?

            [JIM-596] Backslash in now a special character in CSV (JIM and JIRA specific)

            Katherine Yabut made changes -
            Workflow Original: JIM - workflow v2 [ 1611238 ] New: JIM Suggestion Workflow v2 [ 3156434 ]
            Ignat (Inactive) made changes -
            Issue Type Original: Documentation [ 27 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIM Project Workflow (Software Simplified) [ 1606725 ] New: JIM - workflow v2 [ 1611238 ]
            Ignat (Inactive) created issue -

            Roy Krishna (Inactive) added a comment -

            Just to be clear, this is for JIRA 4.4.4 onwards.

            Roy Krishna (Inactive) added a comment - Just to be clear, this is for JIRA 4.4.4 onwards.

            Pawel Niewiadomski (Inactive) added a comment -

            Giles, this issue is no longer valid. Roy decided we switch back to the good, old one CSV parser (https://studio.atlassian.com/browse/JIM-642) so if you did any changes to the documentation please rollback them.

            Pawel Niewiadomski (Inactive) added a comment - Giles, this issue is no longer valid. Roy decided we switch back to the good, old one CSV parser ( https://studio.atlassian.com/browse/JIM-642 ) so if you did any changes to the documentation please rollback them.

            Pawel Niewiadomski (Inactive) added a comment -

            Raised JIM-627 to fix it.

            Pawel Niewiadomski (Inactive) added a comment - Raised JIM-627 to fix it.

            Pawel Niewiadomski (Inactive) added a comment -

            @Roy, as you can see the parse does strange things in some cases. I think we should fix it.

            Pawel Niewiadomski (Inactive) added a comment - @Roy, as you can see the parse does strange things in some cases. I think we should fix it.

            Pawel Niewiadomski (Inactive) added a comment -

            I updated Giles comment with an exact output created by the importer.

            Pawel Niewiadomski (Inactive) added a comment - I updated Giles comment with an exact output created by the importer.

              Unassigned Unassigned
              Anonymous Anonymous
              Archiver:
              dnorton@atlassian.com Dave Norton

                Created:
                Updated:
                Resolved:
                Archived: