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

Import status changed history through JSON does not display as status changed in issue history

      Issue Summary

      Import status changed history through JSON does not display as status changed in issue history. It displays the action but it displays as a plain text. The HistoryItems were transformed into a generic map
      the statements are different when performing it through the UI and when importing using the JSON file
      through the UI, it shows user changed the status while the JSON shows updated

      Steps to Reproduce

      1. Create a JSON file to import issue history of status being changed

      Expected Results

      At the issue history, it is expected that the status is displayed with colored status

      Actual Results

      The HistoryItems were transformed into a generic map

      It's not possible to fetch for these imported issues when performing a JQL search based on the status.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-81943] Import status changed history through JSON does not display as status changed in issue history

            Same issue encountered and this is a big reporting blocker for us migrating data from other trackers... would really like to see this one prioritised. 

            Cam Findlay added a comment - Same issue encountered and this is a big reporting blocker for us migrating data from other trackers... would really like to see this one prioritised. 

            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

            Affects my migration too.

            I've imported history even with mapped status Items (got status IDs first), but nothing. Tried with string type and integer for fields "from"/"to" with no luck.

            {                            
             "author": "61768852f6da6a006ae647c2",                            
             "created": "2022-05-06T10:54:07",                            
             "items": [ {
              "from": "10003",
              "fromString": "Backlog",
              "to": "10000",
              "toString": "To do",
              "fieldType": "jira",
              "field": "status"
             } ]
            } 

            This bug brake a lot of historical data that we wanted to use in reports.

            Anton Balandin added a comment - Affects my migration too. I've imported history even with mapped status Items (got status IDs first), but nothing. Tried with string type and integer for fields "from"/"to" with no luck. { "author" : "61768852f6da6a006ae647c2" , "created" : "2022-05-06T10:54:07" , "items" : [ { "from" : "10003" , "fromString" : "Backlog" , "to" : "10000" , "toString" : "To do " , "fieldType" : "jira" , "field" : "status" } ] } This bug brake a lot of historical data that we wanted to use in reports.

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

                Created:
                Updated: