Forums

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

JSON imports with history data?

Iker Gómez Eiras
Contributor
April 16, 2026

One of our departments needs us to ""clone"" certain issues from one instance to another, including the changelog/history.

From my searches, the only method I've found that might work is using the JSON importer.

But everytime I try to use it with history data, either it ignores the issue data completely, or returns an error.

If I follow the documentation example basically verbatim:
https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-json/
It just ignores the issue. As if it isn't there. So it just does nothing, claims the import is completed and have a good day sir and/or madam.

Instead, if I use "issue" in place of "work item" and "issueType" in place of "workType", it returns an error saying that fields [issue, history] are not valid.
But if I remove the history section, it works like a charm. The issue, with the correct type, correct project, all the data, even the attachments, gets created without a problem.

I'm basically pulling my hair (or what's left of it) off trying to figure out how to do this.

Has anyone here battled with the cloud JSON import system before and could offer some guidance?

1 answer

0 votes
Trudy Claspill
Community Champion
April 16, 2026

Hello @Iker Gómez Eiras 

Is this a one time need or an ongoing need?

If this is a one time or infrequent need I recommend that you explore the Copy Data option for copying data from one Jira Cloud instance to another. That would include the history of the work items.

https://support.atlassian.com/organization-administration/docs/copy-product-data/

To the best of my knowledge (disclaimer - I am not all-knowing ;-) ) it is not possible to directly create history records through either the API or import options. History records are generated automatically by the actions taken on a work item.

If the "cloning" is an ongoing need they you could investigate tools to synchronize work items between Jira instances. As changes are made to the source issue the clone would be updated to match, which would create history for the items in real time.

Suggest an answer

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

Atlassian Community Events