...
The 'Project with Issues' snapshot type includes all issues and related data - attachments, comments, work log entries, issue links, issue history, and many more.Including attachments.
The attachment metadata (filename, creator, create date, etc.) is small enough to always be included in the snapshot. However, 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). A local copy of each file will be made during export regardless of their storage location (local or in Amazon S3). Therefore, you need to have sufficient space available during the export. Once the snapshot is created, these local copies will be deleted.
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 option makes the snapshot size considerably smaller and makes deployment faster. Depending on what type of storage system you’re using, this option’s prerequisites may differ.
If you’re using the local file storage system…
The attachment files for the exported projects will need to be manually copied and moved to a temporary folder
. During
deployment, Configuration Manager will
copy and transfer them from the temporary folder to their correct place in Jira’s attachments directory
using the metadata in the snapshot.
...
If you’re using an Amazon S3 storage system…
You won’t need to copy anything. You’ll just have to provide the attachments directory during deployment. The attachments will be linked up with the help of the metadata in the snapshot.
| Tip |
|---|
Jira stores the attachment files in separate directories by project key.
|
...
|
Create a Project Snapshot with Issues
Choose the cog icon at the top right of the screen, then choose Configuration Manager:
Select Snapshots to open the Configuration Snapshots page and click on the Add Snapshot button.
Select the Project with Issues button and enter a name for the snapshot. Here, you can select as many projects as you need to include in the snapshot. Optionally enter a description. The following screen will appear:
...
When deploying a snapshot with issues, if the attachment files are not included in the snapshot, you can provide a path where the files reside on the target system. Configuration Manager will pick the files from there and attach them to their relevant issues. After the deployment is complete, Configuration Manager will store the files in the Jira attachment directory.
| Info |
|---|
Note that the option to import attachment files from either the file system or S3 will appear in the deployment wizard |
...
only when: |
...
|
To provide attachment path during deployment:
Choose the cog icon at the top right of the screen, then choose Configuration Manager:
Select Deploy on the left menu to open the Deploy Configuration Snapshot page.
Choose a snapshot with issues from the current instance/linked Jira/snapshot file and click the Deploy button. (Read more about deploying snapshots)
There is an option “Do not import issue attachments” in the Advanced Options on the deployment wizard’s Select Deployment Mode.
Either provide a path to import the attachment files or enable the option to skip importing attachment files.
| Infonote |
|---|
Store the attachment files in a temporary folder on the target Jira's file systemyour local system or use a cloud-based storage like Amazon S3. Avoid using Jira’s attachment directory. |
...
...
| Tip |
|---|
...
The attachment path should look like this:
|
...
|
Configuration Manager expects the attachment directories to follow the same structure as Jira’s attachment directory.
E.g.For example, when exporting projects PRA and PRB , on the source server, copy the directories $Jira_Home/data/attachments/PRA and $Jira_Home/data/attachments/PRB, and move them to a temporary directory on the target server, as in the screenshot below:
...
When prompted by Configuration Manager, provide the path to the temp directorytemporary directory. After the deployment, the temporary directory is not needed anymore and can be deleted.
Potential Errors
The provided path does not contain an accessible subdirectory for the project.
If the temp temporary directory does not contain sub-directories for some of the projects in the snapshot, Configuration Manager shows a will show the following warning:
...
After the deployment, the temporary directory is not needed anymore and can be deleted
...
To fix this, you’ll need to either change the path you provided or check the directory’s access rights.
There was an unexpected error related to Amazon S3.
If Configuration Manager fails to authenticate your Amazon S3 storage account, the following error will appear:
...
To fix this, you'll need to check the Jira log, which will contain more detailed information about the error you encountered.