Confluence has been updated to version 6.15.9

JIRA ON-PREMISE JIRA CLOUD ZENDESK AZURE DEVOPS

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.

This article describes how to connect entities from the sync panel.

At the moment, the sync panel is available only for Azure DevOps, Jira Cloud, Jira on-premise and Zendesk. Use the Bulk Connect menu in the Exalate admin console for other platforms. You can also use it to sync entities in bulk in Exalate for Azure DevOps, Jira Cloud, Jira on-premise and Zendesk. For more information, check Bulk Connect.

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 on-premise

There are 2 ways to Connect issues in Exalate for Jira on-premise:

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

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

To connect issues with the Connect button in Jira on-premise:

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

  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 will be 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. The local data filter or remote change processor behavior will be applied. For instance, if the relation specifies that local attachments should remain local, then these will not be sent over.
      • Send all existing worklogs
        All existing work logs will be sent over. The local data filter or remote change processor behavior will be applied. For instance, if the relation specifies that local worklogs should remain local, then these will not be sent over.
      • Sync back
        When this option is selected, all information available on the other side will be synced back to the local issue.

  5. Click Submit to connect issues.

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

Connect issues in Jira Cloud

There are 2 ways to Connect issues in Exalate 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.

  1. Open an issue you want to connect to 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 a 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 work items in Azure DevOps

There are 2 ways to connect work items in Exalate for Azure DevOps:

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

You can connect Azure DevOps work items directly from the work item view.

To connect work items with the Connect button:

  1. Open a work item you want to connect.
  2. Select the Exalate dropdown in the Details tab.
  3. Click Connect.
  4. Select a Connection from the dropdown.
  5. Enter the key of the remote issue you are connecting to in the Remote Issue Urn field.
  6. Specify advanced options if necessary.

    • Connect and sync data
      If enabled, the local issue data will be sent to the destination instance during sync.
    • Sync existing comments?
      If enabled, all existing comments will be sent over. 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 existing attachments?
      If enabled, all existing attachments will be sent over. The source data filter or destination change processor behavior will be applied. For instance, if the connection specifies that source attachments should remain local, then these will not be sent over.

  7. Click Connect.


Connect tickets in Zendesk

To connect a ticket in Exalate for Zendesk:

  1. Open a ticket you want to connect.
  2. Click Apps.
  3. Select the Exalate dropdown.
  4. Click Connect.
  5. Select a Connection from the dropdown.
  6. Enter the key of the remote issue you are connecting to in the Remote Issue Urn field.
  7. Specify advanced options if necessary.

    • Connect and sync data
      If enabled, the local issue data will be sent to the destination instance during sync.
    • Sync existing comments?
      If enabled, all existing comments will be sent over. 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 existing attachments?
      If enabled, all existing attachments will be sent over. The source data filter or destination change processor behavior will be applied. For instance, if the connection specifies that source attachments should remain local, then these will not be sent over.

  8. Click Connect.

See also

How to connect HP ALM defects with existing Jira issues

Comments, attachments, and worklogs not syncing when connecting issues