...
Including the attachment files can make the snapshot grow very large, which is why Configuration Manager allows two ways of handling attachments. The attachment metadata (filename, creator, create date, etc.) is small and is always included in the snapshot.
Include attachment files in the snapshot. This is the preferred option for moving projects with fewer attachments (roughly less than 100 MB).
Do not include attachment files in the snapshot. This is the only viable way to go for moving projects with many (or large) attachments. The attachment files for the exported projects need to be copied and moved to a temporary folder on the target system separately. During the snapshot deployment, Configuration Manager will ask for the path to the directory where the files reside on the target system. It will pick the files from the temp location and copy them to their right places in Jira’s attachments directory, using the metadata in the snapshot. With this option, the snapshot size will be considerably smaller , and will be deployed faster.
Jira stores the attachment files in separate directories by project key in $Jira- $Jira_Home/data/attachments/.
Create a Project Snapshot with Issues
...
| Info |
|---|
Store the attachment files in a temporary folder on the target Jira's file system. Avoid using Jira’s attachment directory. |
...
The attachments attachment path should looks look like this:
C:\temp\attachments (on Windows) or
/somewhere/attachments (on Linux or Solaris)
...