Confluence has been updated to version 6.15.9

This article describes how to start syncing existing issues in Jira.


With the Connect operation, you can sync 2 existing issues between each other. These issues can be in different projects or instances.

Once you connect issues using the Connect operation, all updates will be synchronized automatically according to the sync rules specified in the connection.

At the moment, there is a security vulnerability related to the Connect operation. To avoid it, we recommend making sure that the proxy user doesn't have access to private projects.

Check out this article for more information:

Security Vulnerability — You can access private project data with the Connect operation



Connect Issues in Jira Server

There are 2 ways to Connect issues in Exalate for Jira Cloud:

  • Connect button on the issue view.
  • Bulk Connect option in the Exalate admin menu.

In case the issues you want to connect existing comments, please use the Bulk Connect option in the Exalate admin menu.

Connect Issues Using the Connect Button

  1. Open an issue you want to connect with an issue on the other side.
  2. Select More → Connect from the drop-down.
  3. Add the key of the remote issue you are connecting this issue with.

  4. Set up Advanced options if necessary.

    This section allows specifying if existing comments, attachments and work logs should be synced:

      • Send all existing comments
        The comments which existed before the issue is connected will be sent over to the remote issue. The local data filter or remote change processor behavior is being applied. For instance, if the relation specifies that local comments should remain local, then these will not be sent over.
      • Send all existing attachments
        All attachments that existed before the issue is connected will be sent over (again 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.

  5. Submit to connect issues.

If you want to sync the existing comments, attachments or work logs, make sure you have configured advanced options before submitting.

Connect Issues Using Bulk Connect Issues

  1. Select Bulk Connect issues in the Exalate admin menu.



  2. Select a Connection.
  3. Upload a mapping file.
    The mapping file is a .CSV file with comma-separated issue kye pair. You can create this file with any text editor like notepad. 

    IssueMapping.csv file example
    LOCAL-1, REMOTE-10
    LOCAL-2, REMOTE-8
    LOCAL-4, REMOTE-15

  4. Set up Advanced options if necessary.

    Toggle whether you want to synchronize the existing comments, attachments, and work logs:

      • Sync Comments?
        All the 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 work logs 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.

Click on the Submit button to connect issues.

Connect Issues in Jira Cloud

There are 2 ways to Connect issues in the Exalate app for JIRA Cloud:

  • Connect button on the issue view.
  • Bulk Connect issues option in the Exalate admin menu.

In case the issues you want to connect have existing comments, please use the Bulk Connect issues option in the Exalate admin menu.

Connect Issues Using the Connect Button

  1. Open an issue you want to connect with another issue.
  2. Use the Connect Issues button on the right sidebar (the operation is available only if the issue was not synchronized before).

  3. Select Connection from the drop-down.
  4. Specify the key of the remote issue you are connecting with.
  5. Click on the Submit button to connect issues.

Connect Issues Using Bulk Connect Issues

  1. Select Bulk Connect issues in the Exalate admin menu.



  2. Select a Connection.
  3. Upload a mapping file.
    The mapping file is a .CSV file with comma-separated issue kye pair. You can create this file with any text editor like notepad. 

    IssueMapping.csv file example
    LOCAL-1, REMOTE-10
    LOCAL-2, REMOTE-8
    LOCAL-4, REMOTE-15
  4. Set up Advanced options if necessary.

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

      • 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 work logs?
        All existing work logs 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.

Click on the Submit button to connect issues.

Connect Issues on other Platforms

There is no sync panel on the issue view on other platforms, so you should use the Bulk Connect operation to start synchronizing the existing issues. 

How to connect HP ALM defects with existing Jira issues.


You are evaluating Refined.