Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4225

Import : FileTransferHandler silently throws an HTTP 400 when importing .xml files

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 10.111.0
    • 10.107.4
    • Import|Export
    • 12
    • Severity 3 - Minor
    • No

      Issue Summary

      The POST call to FileTransferHandler silently throws an HTTP 400 error when importing files with a .xml extension.

      Steps to Reproduce

      1. Prepare the import file as usual
      2. Save it with the .xml extension – e.g. import.xml
      3. Browse to the Import your backlog using Excel page, then click the Browse button
      4. Select the import.xml file in the local file system
      • Notice the loading bar animation gets red, very briefly, then vanishes. No work items are displayed (all work item counts are zeroed)

      Expected Results

      • The system accepts xml file without errors.

      Actual Results

      • An HTTP 400 error is thrown in the background
      2022-06-17 23:07:13 172.22.16.138 POST /Handlers/FileTransferHandler.ashx - 443 661683 172.22.18.236 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_15_7)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/102.0.5005.115+Safari/537.36 https://instance.jiraalign.com/ImportObjects?FirstTime=True&Programs=196 400 0 0 375
      • The loading bar animation very briefly displays red, then vanish. No other visual cue or message toaster is presented to the user, informing about the POST call error.

      Workaround

      • In the operating system, rename the import file from import.xml to file.xls

      XML files are typically produced by MacOS users. This is mentioned in Help Center article 10X: Import Objects Via Excel Overview

      For Mac OS users only, when you save the file to import your items back to the system, save the file as a .xml (Excel 2004 XML spreadsheet) file. Then, locate the updated file in your file directory and manually change its extension to .xls. This will format the file so that Jira Align can import it.

        1. image-2022-06-17-20-39-00-225.png
          image-2022-06-17-20-39-00-225.png
          30 kB
        2. Screen Recording 2022-06-17 at 20.37.20.mov
          7.79 MB

            [JIRAALIGN-4225] Import : FileTransferHandler silently throws an HTTP 400 when importing .xml files

            Kyle Foreman added a comment -

            Hello,

            This issue is now fixed (as of the release version on the ticket above). Please let us know if you have any questions!

            -Kyle

            Kyle Foreman added a comment - Hello, This issue is now fixed (as of the release version on the ticket above). Please let us know if you have any questions! -Kyle

            Lois Martin added a comment -

            A warning when the failure occurs will definitely improve the experience. However, it appears that Atlassian has changed the expected behavior. Jira Align has always stressed using the most recent import template exactly as it is and only adding your data. Since the import template downloads as an XML file (for all work item types), it has also been important to save it and import as an xml file. But now you seem to be saying that we should be saving the template and using it as an xls file instead.

            Lois Martin added a comment - A warning when the failure occurs will definitely improve the experience. However, it appears that Atlassian has changed the expected behavior. Jira Align has always stressed using the most recent import template exactly as it is and only adding your data. Since the import template downloads as an XML file (for all work item types), it has also been important to save it and import as an xml file. But now you seem to be saying that we should be saving the template and using it as an xls file instead.

              97abbabfa9ae Chase Nielson
              rcortez@atlassian.com Rodrigo Cortez
              Affected customers:
              6 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m