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

JSON import results in history being updated as "Anonymous user"

XMLWordPrintable

      Issue Summary

       
      After JSON import, issues successfully get created and when checking the history of the issue, we see that the "Rank" is being updated by the Anonymous user, which is a concern to find who is the "Anonymous user".

      Steps to Reproduce


      1. External system import -> choose Json

      2. Upload the JSON file

      3. Once the import completes successfully, check the issue history and you will find the rank field being updated by "Anonymous user".

      Expected Results

      The user name should be displayed or if this is Jira system, then some relevant user ID should be updated rather using the term "Anonymous user".

      Actual Results

      As highlighted, the Rank is updated by "Anonymous user".
       

      Workaround

      Currently there is no known workaround for this behavior. 

        1. image-2021-03-10-19-30-58-454.png
          image-2021-03-10-19-30-58-454.png
          271 kB
        2. image-2021-03-10-19-32-47-333.png
          image-2021-03-10-19-32-47-333.png
          271 kB
        3. Screenshot 2024-04-19 at 4.29.25 PM.png
          Screenshot 2024-04-19 at 4.29.25 PM.png
          53 kB
        4. Screenshot 2024-04-19 at 8.06.34 PM.png
          Screenshot 2024-04-19 at 8.06.34 PM.png
          90 kB

            [JRACLOUD-82052] JSON import results in history being updated as "Anonymous user"

            Chung Jeon added a comment -

            i could have reproduced it with csv from external import also.

            Chung Jeon added a comment - i could have reproduced it with csv from external import also.

            Creative Quality S.L. added a comment -

            I check some minutes ago, that occurs in CSV import too, so there is some "field" that "throw" the rank change when is imported.

            Creative Quality S.L. added a comment - I check some minutes ago, that occurs in CSV import too, so there is some "field" that "throw" the rank change when is imported.

            Creative Quality S.L. added a comment -

            The issue still continues. In my case, i dont work with "ranks", and i try with no rank field in json, and with rank field empty in json, and always fail with rank low.

            As Nathan say, this change the history and the last updated datetime, so generates a lot of "recent" issues.

            Creative Quality S.L. added a comment - The issue still continues. In my case, i dont work with "ranks", and i try with no rank field in json, and with rank field empty in json, and always fail with rank low. As Nathan say, this change the history and the last updated datetime, so generates a lot of "recent" issues.

            Nathan Neulinger added a comment -

            Bigger issue than the 'anonymous user' aspect is that this results in 100% of imported content showing as "modified today" as of the date of the import - no matter how old the imported issues are. 

            Nathan Neulinger added a comment - Bigger issue than the 'anonymous user' aspect is that this results in 100% of imported content showing as "modified today" as of the date of the import - no matter how old the imported issues are. 

              Unassigned Unassigned
              c1c38b0b1b95 Priyadharshini CS (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated: