Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-342

Unable to set Due Date field using the Look and Feel configuration

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Issue Summary

      Importing Due Date in the format set in the Global Settings (look and feel) causes the import to fail for Due Date field as it uses its own format YYYY/MMM/dd.
      When importing the Due Date value, it gives a warning that Jira was unable to parse the value.

      Steps to Reproduce

      1. Have the look and feel set to display and use dates in the format MMM/dd/yy
      2. Have a CSV file to import and set the Due Date
      3. At the CSV import wizard set the date format to match your data format MMM/dd/yy

      Expected Results

      The import should finish with success mapping the Due Date field as expected.

      Actual Results

      It gives an error that Jira was unable to parse the date format.

      Workaround

      Use the default format at the CSV file (I.e 03/Mar/20 12:00 AM) and at the import wizard leave the default format suggestion: dd/MMM/yy h:mm a

        1. Screenshot 2020-05-26 at 2.03.26 PM.png
          Screenshot 2020-05-26 at 2.03.26 PM.png
          412 kB
        2. Screenshot 2020-05-26 at 2.03.50 PM.png
          Screenshot 2020-05-26 at 2.03.50 PM.png
          325 kB
        3. Screenshot 2020-05-26 at 2.05.41 PM.png
          Screenshot 2020-05-26 at 2.05.41 PM.png
          326 kB
        4. Screenshot 2020-05-26 at 2.06.25 PM.png
          Screenshot 2020-05-26 at 2.06.25 PM.png
          248 kB

            [MIG-342] Unable to set Due Date field using the Look and Feel configuration

            Andrew T added a comment -
            Atlassian Update - September 22, 2023

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug considering its priority and impact to focus on our upcoming roadmap for all customers.

            As we continue to roll out features we do look at requests made by our customers and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Migrations team

            Andrew T added a comment - Atlassian Update - September 22, 2023 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open , we are closing this bug considering its priority and impact to focus on our upcoming roadmap for all customers. As we continue to roll out features we do look at requests made by our customers and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Migrations team

            Ankita Gupta added a comment - - edited

            dbraun@atlassian.com

            Tried same steps to reproduce issue but it worked for me. I have attached screenshots for the reference. For the case when customer faced the issue, date format chosen by customer while importing might not be same used in csv. Can you please confirm?

             

            Looking at screenshots attached in https://getsupport.atlassian.com/browse/JST-560212, customer chose dd/MMM/yy format during csv import but csv contains due date in format dd/MM/yy. 

            Ankita Gupta added a comment - - edited dbraun@atlassian.com Tried same steps to reproduce issue but it worked for me. I have attached screenshots for the reference. For the case when customer faced the issue, date format chosen by customer while importing might not be same used in csv. Can you please confirm?   Looking at screenshots attached in  https://getsupport.atlassian.com/browse/JST-560212 , customer chose dd/MMM/yy format during csv import but csv contains due date in format dd/MM/yy . 

              Unassigned Unassigned
              dbraun@atlassian.com Douglas B (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: