JIRA Import Wizard is not clear on the format needed to import a Cloud Export

Summary

When doing a JIRA Cloud import at /secure/admin/StudioImportSelect!start.jspa the JIRA Import Wizard:

1. fails to import a JIRA Cloud export
2. is not clear on additional steps that have to be performed if the export is from JIRA Cloud
3. can use a rewording for easy reading and differentiating Important Notes, Steps and Prerequisites.

This Bug request is to correct the Wording on the JIRA Import Wizard to address all types of JIRA imports and prevent Cloud import failures in case it keeps not accepting direct Cloud exports as Suggested in: JRA-59604

Environment

• JIRA Cloud

Steps to Reproduce

1. Export JIRA Cloud with Attachments
2. Upload file to webdav
3. Go to JIRA Import section
4. read carefully the notes
5. Click next
6. Select a JIRA Cloud export
7. Import

Expected Result:
JIRA Imports correctly with attachments as it is the same server export.

Actual Results:
Import fails
Sometimes due to Attachment problems JRA-42738, or Memory problems.
It never imports attachments.

Notes

The Import Wizard has a list of Prerequisites that are not clear enough for an administrator to follow the correct steps and avoid problems:

Prerequisites

1. An export of your existing JIRA instance.
2. Optionally, compressed copies of:
   <JIRA_HOME>/data/attachments directory. The contents should either have the attachments directory as the top level directory, or the project keys within the attachments directory as the top level directories.
   <JIRA_HOME>/data/avatars directory. The contents should have the avatars directory as the top level directory.
   <JIRA_HOME>/logos directory. The contents should have the logos directory as the top level directory.
3. Please note that your JIRA instance will not have any issues attachments, user avatars or project logos if they are not restored along with your exported JIRA data.

1. The export is Cloud JIRA export
2. The #2 step is optional.
3. The #3 is a Note and not a Prerequisite and it's wrong because Attachments can be imported afterwards using the same importer.

It also doesn't mention that the user base in common with Confluence will be wiped out.
It also has a link to missing documentation: https://confluence.atlassian.com/display/Cloud/Importing+Issues

Workaround

Follow How to restore a JIRA Cloud application backup into another JIRA Cloud application