Show an error message accordingly when the Import Attachments fail to import the attachments

XMLWordPrintable

    Problem Definition

    When doing a site import, we can now opt to do the import without attachments and import the attachments later using the Import Attachments feature, to properly import the attachments, the folders within the zip file needs to follow a respective structure which is described in the How to import only part of a Jira export into Jira Cloud

    attachments-only.zip
    └─── data
          ├── attachments
          │         ├── ProjectKey
          │         │         └── 10000
          │         │		├── IssueKey-1
          │         │		├── IssueKey-2
          │         │       	└── IssueKey-3
          │         ├── ProjectKey2
          │         └── ProjectKey3
          └── avatars
    

    When importing the attachments, if the folders inside the zip file aren't following exactly the structure above, e.g. the folder 10000 between the project key and issue key is missing, the import will complete and it will show a message that the import succeeded, however, the attachments aren't imported.

    Suggested Solution

    Have a verification before the import starts stating that the structure within the zip file isn't correct and show what's wrong in the backup folder, or at least show an error message with the page mentioned above informing to check the folder's structure within the backup making sure that they follow the exactly the same structure as the one described in the page.

    Why this is important

    The import succeeded message after the import even when the attachments aren't correctly imported due to a wrong folder structure totally mislead with the actual result, therefore, it would be good to have this accurate message stating that the attachments actually weren't imported due to a wrong folder structure.

    Workaround

    N/A

          Assignee:
          Unassigned
          Reporter:
          Francisco Oselame (Inactive)
          Votes:
          1 Vote for this issue
          Watchers:
          7 Start watching this issue

            Created:
            Updated:
            Resolved: