Confluence has been updated to version 6.15.9

With Bulk Connect you can sync a set of entities with one operation.

In Exalate for Jira on-premise, Jira Cloud, Azure DevOps, and Zendesk, you can use the Connect Operation to sync each issue manually.


To sync issues in bulk:

1. Navigate to the Bulk Connect tab in the Exalate admin console.

2. Select a Connection from the dropdown.

3. Select the entity type to bulk connect.

(warning) This step is applicable only to the work management systems where Exalate supports multiple entities.


You can select a specific entity type to apply bulk connect to, in case Exalate on your platform supports multi-entity synchronization.

4. Upload a .csv file with the Issue Mapping.

The .csv file should contain comma-separated issue key pairs that will be synced. The issue keys within a pair should be separated by a comma.

(warning) If your platform supports multiple entities, make sure that the .csv file includes correct entity type keys, corresponding to the entity type selected earlier.

Example of an issue mapping file:

LOCAL-1, REMOTE-4
LOCAL-2, REMOTE-5
LOCAL-4, REMOTE-6
LOCAL-5, REMOTE-9

In this example, the issue LOCAL-1 will be synced to the issue REMOTE-4, LOCAL-2 to REMOTE-5, and so on.

Exalate generates the file automatically each time you do clean-up by connection. The file is located in {$JIRA_HOME}/exports/ directory.

You can recognize the file by its name. It includes connection name, date and time data when it was generated.

Here's an example of such file: connect-RELATION-A to B-20190425_122209.csv 

5. Configure Advanced options.

Toggle whether you want to synchronize existing comments, attachments, and worklogs.

Descriptions of toggles:

  • Connect and sync data
    If enabled, the local issue data will be sent to the connected issue on the destination instance during sync.
  • Sync existing comments?
    If enabled, all existing comments will be sent over. The source outgoing sync rules or destination incoming sync rules will be applied. For instance, if the connection specifies that source comments should remain local, then the source comments will not be sent over.
  • Sync existing attachments?
    If enabled, all existing attachments will be sent over. The source outgoing sync rules or destination incoming sync rules will be applied. For instance, if the connection specifies that source attachments should remain local, then the source attachments will not be sent over.
  • Sync existing worklogs?
    If enabled, all existing worklogs will be sent over. The source outgoing sync rules or destination incoming sync rules will be applied. For instance, if the connection specifies that source worklogs should remain local, then the source worklogs will not be sent over.

6. Click Bulk Connect to start the sync.

After a successful sync, you will see the success message with details. 

  

See also

Connect operation

HP ALM/QC: How to sync existing defects with remote issues in Jira

Comments, attachments, and worklogs not syncing when connecting issues