Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-81965

CSV import do not create line break for text field when user tick the Map field value option

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Description

      Customer have a CSV file and contains a description filed. The value of the description file is formatted to have line break between lines. When customer import the CSV file and tick the Map field value option, JIRA will remove the line break between lines and import.

      Step to reproduce

      1. Create a CSV file and add a description column.
      2. Enter multiple sentence and line break between the sentence for description field
      3. Login to JIRA
      4. Go to External Import System
      5. Upload the CSV file
      6. Proceed to Map fields page
      7. Tick Map field value for description field and click next
      8. JIRA show the description value without any space between lines
      9. Click Begin Import
      10. Check the imported issue and found out the line break between sentence is removed.

      Expected Result

      JIRA should not remove the line breaks and space between paragraph and sentences when import.

      Workaround

      Do not tick the Map field value option in Map value page

            [JRACLOUD-81965] CSV import do not create line break for text field when user tick the Map field value option

            Hello!

            We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.

            Survey link - https://forms.gle/NYNkmS92r96z42QV9

            Thanks!

            Prashanth M
            Product Manager, Jira Platform

            Prashanth M added a comment - Hello! We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to  fill out this survey . Your feedback will help us learn how we can improve your experience in importing data. Survey link -  https://forms.gle/NYNkmS92r96z42QV9 Thanks! Prashanth M Product Manager, Jira Platform

            Any update on this? any ETA?

            Sachin Dhamale added a comment - Any update on this? any ETA?

            Same here, line breaks in CSV aren't coming through into Description field in JIRA. Please fix asap.

            Urs.Kemmann added a comment - Same here, line breaks in CSV aren't coming through into Description field in JIRA. Please fix asap.

            Happened to me also, Please fix this issue ASAP. I wasting my time just to fix the CSV 

            dwike.aprilia added a comment - Happened to me also, Please fix this issue ASAP. I wasting my time just to fix the CSV 

            S Fong added a comment -

            This impacts my team and wonder when you can fix it?

            S Fong added a comment - This impacts my team and wonder when you can fix it?

            Hi Tim, sorry that link isn't under my control, just a page I found during a Google search and wanted to credit the page that helped me form this (limited) workaround.

             

            Stuart Wighton added a comment - Hi Tim, sorry that link isn't under my control, just a page I found during a Google search and wanted to credit the page that helped me form this (limited) workaround.  

            Tim Ervin added a comment - - edited

            Figured out how to mak this work as expected.

            Can the Workaround stated in the description please be updated to reflect the current state of that screen? "Map field value" on the Map fields screen is different from "Target value in JIRA" on the Map values screen. I read the workaround and it made no sense to me. It could have saved me a lot of time and frustration.

            Tim Ervin added a comment - - edited Figured out how to mak this work as expected. Can the Workaround stated in the description please be updated to reflect the current state of that screen? "Map field value" on the Map fields screen is different from "Target value in JIRA" on the  Map values screen. I read the workaround and it made no sense to me. It could have saved me a lot of time and frustration.

            Tim Ervin added a comment - - edited

            @stuart wighton: can you make the Confluence link above public?

            This makes importing from CSV borderline useless. The double-slash workaround still breaks bullets, numbered lists, and header formatting. Going through hundreds of issues to add formatting makes my job tedious and unfulfilling.

            Tim Ervin added a comment - - edited @stuart wighton: can you make the Confluence link above public? This makes importing from CSV borderline useless. The double-slash workaround still breaks bullets, numbered lists, and header formatting. Going through hundreds of issues to add formatting makes my job tedious and unfulfilling.

            Stuart Wighton added a comment - - edited

            This might not suit your circumstances, however I've just imported a number of issues created in Excel and was able to inject a  double backslash
            between the description text and this results in line breaks.

            e.g. formula to build string:

            = A1 & " \\ " & A2 & " \\ " & A3

            or:

            Line 1: abc xyz. \\ Line 2: abc xyz. \\ Line 3: abc xyz.

            Saving as a csv and importing into JIRA gives this formatted result in the description:

            Line 1: abc xyz.
            Line 2: abc xyz.
            Line 3: abc xyz.

             Edit: Double slash formatting caused line breaks in comment, #irony 

            Reference: https://intenso.atlassian.net/wiki/spaces/FLO/pages/21987785/CSV+Importer+does+not+handle+new+lines 

             

            Stuart Wighton added a comment - - edited This might not suit your circumstances, however I've just imported a number of issues created in Excel and was able to inject a  double backslash between the description text and this results in line breaks. e.g. formula to build string: = A1 &  " \\ " & A2 & " \\ " & A3 or: Line 1: abc xyz. \\ Line 2: abc xyz. \\ Line 3: abc xyz. Saving as a csv and importing into JIRA gives this formatted result in the description: Line 1: abc xyz. Line 2: abc xyz. Line 3: abc xyz.  Edit: Double slash formatting caused line breaks in comment, #irony  Reference: https://intenso.atlassian.net/wiki/spaces/FLO/pages/21987785/CSV+Importer+does+not+handle+new+lines    

            Hi. we are trying to migrate from a on-prem to Atlassian cloud jira. We have over 500 issues to migrate. All these issues have full descriptions with line and paragraph breaks.

            I can export the details correctly, the Import CSV file has all the correct line breaks, yet once imported it is all lost. WOW!!!!!

            Atlassian, if you want companies to move to the cloud then start making it easy.

            I am going to have to manually massage the imported issue tickets, WOW!!!!! What a WASTE of my time.

            Please put some effort into helping YOUR customers use Your tools.

            System Migration added a comment - Hi. we are trying to migrate from a on-prem to Atlassian cloud jira. We have over 500 issues to migrate. All these issues have full descriptions with line and paragraph breaks. I can export the details correctly, the Import CSV file has all the correct line breaks, yet once imported it is all lost. WOW!!!!! Atlassian, if you want companies to move to the cloud then start making it easy. I am going to have to manually massage the imported issue tickets, WOW!!!!! What a WASTE of my time. Please put some effort into helping YOUR customers use Your tools.

              Unassigned Unassigned
              lng@atlassian.com Lipkent Ng
              Affected customers:
              26 This affects my team
              Watchers:
              46 Start watching this issue

                Created:
                Updated: