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

Provide an option to not update the “Updated Date” when doing a CSV import.

    XMLWordPrintable

Details

    • 25
    • 14
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      Lets say a user wants to import the QA_Contacts field from a Bugzilla instance. As this field cannot yet be imported as per this feature request: https://ecosystem.atlassian.net/browse/JIM-533

      So the logical thing to do is to import the field separately via CSV import. The problem here is that the Updated field of the issue will be overwritten with the latest date. This is a big problem for customers who want to preserve historical data on older, closed tickets.

      Even if you manually specify the Updated field to a column in the CSV file, the CSV importer does not import those values and the Date Updated field will be set to the latest date, and not to the value you specified in the CSV import.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Anonymous Anonymous
              Votes:
              47 Vote for this issue
              Watchers:
              55 Start watching this issue

              Dates

                Created:
                Updated: