-
Bug
-
Resolution: Unresolved
-
Medium
-
32
-
Severity 3 - Minor
-
4
-
Issue Summary
JSON importer does not accept accountIDs for history data
Steps to Reproduce
- Create a JSON import file and specify a history / change log data to import.
- Use AccountID for the author.
- Import into JIRA using the JSON importer
{
"projects": [
{
"name": "BURNUP",
"key": "BUR",
"type": "software",
"issues": [
{
"key" : "BUR-134",
"status" : "TO DO",
"reporter" : "5570XXXXXXXXXXXXXX",
"summary" : "Parent case",
"externalId": "134",
"history" : [
{
"author" : "5570XXXXXXXXXXXXXX",
"created": "2019-08-11T15:59:02.161+0100",
"items": [
{
"fieldType" : "jira",
"field" : "status",
"from" : "3",
"fromString" : "In Progress",
"to" : "10006",
"toString" : "To Do"
}
]
},
{
"author" : "5570XXXXXXXXXXXXXX",
"created": "2019-09-21T15:59:02.161+0100",
"items": [
{
"fieldType" : "jira",
"field" : "status",
"from" : "3",
"fromString" : "In Progress",
"to" : "10006",
"toString" : "To Do"
}
]
}
]
}
]
}
]
}
Expected Results
On the imported data, the changelog author should correlate to the accountID
Actual Results
The imported data, shows "unknown" user.
Workaround
Set the changelog author to the accounts username if that is known.
[JRACLOUD-81929] JSON importer does not accept accountIDs for history data
Support assisted with finding a solution. The workaround provided in https://jira.atlassian.com/browse/MIG-356 where you duplicate the first history item you are trying to add in your JSON, seems to work in case your history items are not importing whatsoever.
Combine the workaround provided in MIG-356 (duplicate the first history item for each issue) with the workaround provided here (use intenral IDs provided by support) and you should be able to get your history import working.
Possibly related to this, using account IDs will not even display any history data anymore. The import won't fail, but no history data will be imported whatsoever.
Thank you for your reply and the suggestion Karsten.
I applied the below workaround and it worked.
- Installed Jira Server using atlas-run on my local PC.
- Imported the json into Jira Server. Project and history items are inserted successfully into Jira Server on my local PC.
- Migrated the project from Jira Server to Jira Cloud using Cloud Migration Assistant.
@Mehmet I solved this by putting in a support request, which got me a list of the imported users with their internal ID, which could then be used for the import.
I am facing the same problem. I tried with accountId, displayName, email, email prefix till @ character. None of them worked.
With the Jira GDPR changes there is no username in cloud. So the workaround does not work.
I'm currently facing the same problem, but I have noticed something: After import, the changelog in the issue itself shows only "user" (not "anonymous user", which is shown when no author is available), and the tooltip for this user says "Oops, looks like we’re having issues\nTry again and we’ll give it another shot". But the activity stream for the project shows the string that was in the author field, and without a link to the user profile. So the string must be stored somewhere.
For user fields outside of the history importing works when giving id or name which matches the name of the "user" element in the JSON, as specified in the docs. Only history entries show this behaviour.
Any update on this, I too am only seeing 'User' in the history section for changes, after trying to import history through json. I have tried full name, email, internal Atlassian user id
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