Move Attachments

 

On this page:

Introduction

The 'Project with Issues' snapshot type includes all issues and related data - attachments, comments, work log entries, issue links, history, and many more.

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.

  1. Include attachment files in the snapshot. This is the preferred option for moving projects with fewer attachments (roughly less than 100 MB).

  2. 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_Home/data/attachments/.

Create a Project Snapshot with Issues

  1. Choose the cog icon at the top right of the screen, then choose Configuration Manager:

  2. Select Snapshots to open the Configuration Snapshots page and click on the Add Snapshot button.

  3. 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:

 

Deploying a Snapshot with Issues

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.

Note that the option to import attachment files from the file system will appear in the deployment wizard, only when:

  • When at least one issue in the snapshot has an attachment, and

  • The attachment files are not included in the snapshot.

To provide attachment path during deployment:

  1. Choose the cog icon at the top right of the screen, then choose Configuration Manager:

  2. Select Deploy on the left menu to open the Deploy Configuration Snapshot page.

  3. Choose a snapshot with issues from the current instance/linked Jira/snapshot file and click the Deploy button. (Read more about deploying snapshots)

  4. There is an option “Do not import issue attachments” in the Advanced Options on the deployment wizard’s Select Deployment Mode.

  5. Either provide a path to import the attachment files or enable the option to skip importing attachment files.

Store the attachment files in a temporary folder on the target Jira's file system. Avoid using Jira’s attachment directory.

The attachments path should looks like:

  • C:\temp\attachments (on Windows) or

  • /somewhere/attachments (on Linux or Solaris)

Configuration Manager expects the attachment directories to follow the same structure as Jira’s attachment directory.

E.g., 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 directory.

If the temp directory does not contain sub-directories for some of the projects in the snapshot, Configuration Manager shows a warning:


After the deployment the temporary directory is not needed anymore and can be deleted.