Confluence has been updated to version 6.15.9


With Bulk Connect you can synchronize a set of issues with one operation.

In Exalate for Jira Server and Jira Cloud, you can use the Connect Operation to sync each issue manually.

To configure such synchronization, please navigate to Bulk Connect tab in the Exalate admin menu and follow the steps below:

  1. Select the Connection

  2. Upload the mapping file, you've created previously with the issue mapping.

    The issue mapping.csv file should contain comma-separated issue-issue key pairs:

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

    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 

  3. Configure Advanced options

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

      • Sync Comments?
        All existing issue comments will be sent over to the remote issue. The source data filter or destination change processor behavior will be applied. For instance, if the connection specifies that source comments should remain local, then these will not be sent over.
      • Sync attachments?
        All existing attachments will be sent over (again respecting the data filter and change processor).
      • Sync worklogs?
        All existing worklogs will be sent over (respecting the data filter and change processor)
      • Sync back
        When this option is selected, all information available on the other side will be synced back to the local issue.

  4. Bulk Connect to start the synchronization. You will see the success message with details. 

   

Congratulations! Now you know how to synchronize existing issues with the remote instance.


See Also

Connect operation

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