JSON importer fails without log when importing issue history items

[Matt Ward]

Hello, 

I've been doing an import from an older ticketing system using the JSON import tool into our Jira cloud application, following guidance available here: https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html (at time of writing, this document was last modified on 9/1/2019).

If I remove the "history" node from my import JSON, I have no issue whatsoever; issues import fine.  If I retain the "history" node (complete with "author", "created" and "items") per the examples given on that, the import fails at the validation stage with that error message.

When I attempt to load the import log via the provided link, the response is a HTTP 410 Gone.

I've looked at similar issues on Atlassian community and it seems like these are answered on a case-by-case basis.  It would be really helpful if there were a JSON schema I could refer to; otherwise - particularly without logging - this is somewhat of a black box.

Any assistance in this matter would be greatly appreciated!

Thanks in advance.

[Belto]

Issue was resolved by the user by correcting the following:

1. Ensuring that referred statuses have no
surrounding whitespace.

2. Exactly matching every letter - including case - to existing statutes.
If one is inaccurate, the entire import fails.

3. The exported data treated arrays/lists almost unconditionally as
objects/dictionaries, which - when serialized into JSON form - was rendered
as an object with consecutive object indices. This was a fault of the
language used in this pseudo-ETL approach to building the import JSON.

4. Wrong field type given for the out-of-the-box custom fields "Epic Link"
(com.pyxis.greenhopper.jira:gh-epic-link) and "Epic Name"
(com.pyxis.greenhopper.jira:gh-epic-label).