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. 

Examples

Scenario A:

  • User A uploads an attachment in project A

  • This is synced to project B by Backbone

  • User A removes the attachment in project A

  • Backbone removes the attachment in project B (this can be disabled in the advanced settings with sync.disableAttachmentDeletion)

Scenario B:

  • User A uploads an attachment in project A

  • This is synced to project B by Backbone

  • Someone deletes the attachment on project B

  • Backbone won’t remove the attachment in project A as this one was not added by Backbone.

Further configuration

You can configure additional options via the configure link 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 (Whitelist Mapping)/excluded from (Blacklist Mapping) 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 (Whitelist Mapping)/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.