Attachments (email/file exchange)
In the attachments tab, you can define whether attachments are synchronized between instances. Attachments have to be activated on the master side before they can be activated on the slave side as well.
Define how attachments are synchronized between instances.
Deletions
- If an attachment gets deleted in the issue where it was originally added, it will also be removed in the corresponding issue in the partner project.
- If you delete an attachment that has been synchronized to the partner project by Backbone, it will not be removed in the issue in the partner project where it was added originally.
Further configuration
You can configure additional options via the filters links for both directions. There you can choose between two modes:
- Exclude Mapping (default). This synchronizes all attachments in the synchronization except the ones you specify with the filter options.
- Include Mapping. Only attachments matching the filter options will be synchronized.
Filter options
- Maximum file size. Files bigger than the specified file size will not be synchronized. The file size is specified in MB.
- Mime Types. Files with a mime type from this list will be included in / excluded from the synchronization. You can find a list of possible mime types here (use the template).
- Filename Regex. Files with a name matching this regular expression will be included in / excluded from (Blacklist Mapping) the synchronization. The regular expression will be executed in Java, so you can use any regular expression which works in Java.
Jira Service Management
In Jira Service Management attachments are marked as "internal" or as "shared with customers" ("public"). This information is stored in comments where the attachments are in. Therefore the synchronization of comments needs to be enabled in the same direction as the synchronization of attachments. You can enable or disable attachment syncs with the same visibility settings as applied to comments.
If you synchronize attachments from a Jira Software project to a Jira Service Management project, the attachment visibilities will be set as configured by the comment settings. Within this process comments in the Jira Service Management project might be generated.
- Enable the comment synchronization in both directions
- Switch to the attachment tab
- You can now see the same visibilities as set up in the comments tab
- Click both checkboxes
More information about comment configuration can be found in Comments.
If all comment visibilities of one direction are mapped to "ignore", the attachment synchronization is not available for this direction.
- Enable the comment synchronization
- Switch to the attachment tab
- You can now see the same visibilities as set up in the comments tab
- Click the checkbox
More information about comment configuration can be found in Comments.
If all comment visibilities are mapped to "ignore", the attachment synchronization is not available.
If you have a configuration from older Backbone versions with attachment synchronizations active, you can still use this configuration. However, a message will be shown if the comment synchronization is not enabled or not enabled for the attachment synchronization direction. You can then only disable the attachment synchronization or change the comment synchronization direction. Please consider synchronizing comments in the same direction.
