Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

while uploading history using json , the user field cannot editable

Dharani Dharan D
June 8, 2026

{

history{

author:"account_id"

}

}

while uploading history using json , in author field i give account id , but it shows anonymous user in UI , the user is exists on the instance 

1 answer

2 votes
Artem Nek_Votazz
Atlassian Partner
June 8, 2026

Hi @Dharani Dharan D 

Short version: this is a known limitation, not a problem with your JSON.

For the importer to attribute history to a real user, that user has to be defined
in the top-level "users" array and the history "author" must match its "name"
exactly — on Cloud that's the accountId. The official format example shows it:
https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-json/

But on Cloud, account IDs in the history author are a documented bug — they come
through as anonymous/unknown even when set up correctly. It's tracked (still open)
here: https://jira.atlassian.com/browse/MIG-376

So make sure the user is defined in the "users" array first — that clears the
plain missing-definition cases. If it still shows anonymous after that, you're
hitting MIG-376 rather than a config error, so it's worth voting and watching it
for updates.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events