The Connect feature allows syncing existing issues in-between. It helps to synchronize existing issues in different projects or instances.


Connect issues on Jira Server

There are 2 ways to Connect issues in the Exalate app 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 have existing comments, please use Bulk Connect option in the Exalate admin menu.

Connect issues using Connect button

  1. Open an issue you want to connect with another issue
  2. Select More > Connect (the operation is available only if the issue was not synchronized before)

  3. Select the Connection from the drop down
  4. Specify the key of the remote issue you are connecting with

  5. Advanced options

    This section allows specifying if existing comments, attachments and worklogs 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.

  6. Click Submit button to connect issues.

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

Connect issues using Bulk Connect issues

  1. Select Bulk Connect issues in the Exalate admin menu



  2. Select a Connection
  3. Upload mapping file
  4. 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.

Click Submit button to connect issues.

Connect issues on 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 Bulk Connect issues option in the Exalate admin menu.

Connect issues using Connect button

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

  3. Select the Connection from the drop down
  4. Specify the key of the remote issue you are connecting with
  5. Click 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 mapping file
  4. 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.

Click Submit button to connect issues.

Troubleshooting

 

When a sync error appears or the remote issue doesn't exist you will get an error notification and the status result in the sync status panel.

As a user you will see:

The error can be resolved only by the Exalate administrator. 

In case you need help, please submit a request at support@exalate.com.

We are improving the product so that the user will get notified if the issue cannot be connected, and provide a way to rectify (instead of the administrator).

 

See Also 

How to connect HP ALM defects with existing Jira issues.