Improve the external import developer documentation

I may be in minority here - I find that the external import developer documentation (located https://developer.atlassian.com/cloud/insight/rest/api-group-import/#api-import-start-id-post, https://developer.atlassian.com/cloud/insight/imports/introduction/ and https://developer.atlassian.com/cloud/insight/imports/workflow/ and https://developer.atlassian.com/cloud/insight/imports/schema-and-mapping/) seems to be lacking clarity on various subjects. The docs are definitely helpful and I believe can be improved upon.

Here are some examples:

• What should the schema/mapping payload JSON include when only pushing object data where changes to the object types/attributes are not required. It took me several hours of trying different payloads to figure out that I only needed to include the objectType without any attributes (in retrospect this seems evident - for whatever reason it didn't click in my head).
• The PUT call described is only for the initial creation of the object types and attributes and PATCH needs to be used going forward with regular updates.
• The REST API document only describes two (the POST to start the mapping and the GET for progress) of the eight APIs. The following APIs aren't covered:
  • GET https://api.atlassian.com/jsm/insight/v1/imports/info
  • getStatus
  • mapping - PUT
  • mapping - PATCH
  • submitResults
  • getExecutionStatus
  • cancel
• What is and isn't supported in the API versus the UI. For example, configuring any of the attribute's properties (Include children, Unique, Cardinality, or Filter objects) through the import API is not supported. I realized this because I've messed with the UI enough to understand the gaps, it would be helpful though to call these out in documentation instead of leaving the reader to figure this out because they aren't defined.