Confluence has been updated to version 6.15.9

JIRA CLOUD ZENDESK JIRA SERVER AZURE DEVOPS

After establishing a connection, you need to set up the sync scope. In the scope, you specify the details: what issues should be synchronized and how to start the synchronization process.

To configure the scope:

1. Start scope configuration.

  • To start setting up the scope after establishing a new connection click Configure sync.
  • To configure synchronization in an existing connection, navigate to ConnectionEdit connection.


The visual editor will be available only if you verify admin access on your end.

2. Select what to synchronize.

Depending on the issue tracker you use, you will synchronize projects with issues, tickets, or other entities.

To synchronize projects, select a project from the Select project list.

Specify the criteria for tickets and other entities in the Filter entities menu.

3. Set the synchronization method in the Sync method list.

In the Sync method list, you can define how the data will be synced between your issue trackers.

You can choose between the following options:

Manual
The issues will be synced manually between various trackers.
Automatic
The issues will be synchronized automatically according to the filters that you set up.
Disabled
Issues won't sync in the specified direction.

Issues will be synced in the direction defined by the arrow.

4. Apply filters if necessary.

To apply filters to projects:

  1. Click Filter issues.
  2. Set the filters.

The filters are different depending on the issue tracker. For example, issues in Jira have issue types, and tickets in Zendesk have types. So, the type filter for Jira is called Issue types and Types for Zendesk tickets.

After you apply the filters, only certain issue types from Jira and ticket types from Zendesk will sync with one another.

Issue filter for Jira Cloud and Jira Server

Multiple filter options for one filter type will be considered OR operation. Different types of filters will be considered AND operations.

Check out the examples below:

Issue type = Bug
Priority = High, Medium 
Status = Open

In this case, the Priority filter has 2 options assigned. Only the issues of the type Bug AND with the priority High OR Medium AND with the status Open will be synced. 

So, there are 2 possible combinations for the sync:

1) Bug with the High priority and Open status,

2) Bug with the Medium priority and Open status.

If there are no options selected for the issue type, like in the example below:

Priority = High, Medium 
Status = Open

All issue types with the priority High OR Medium and status Open will be synced.

The following combinations are possible:

1) Any existing issue type (bug/task/story/...) with the priority High and status Open

2) Any existing issue type (bug/task/story/...) with the priority Medium and status Open

Issue filter for Zendesk

Filter example:

Status = Open, Hold
Type = Task
Priority = Urgent

In this case, the following combinations will be synced:

1) Task with the Open status and Urgent priority

2) Task with the Hold status and Urgent priority


Issue filter for Azure DevOps

Filter example:

Type = Task, Issue
State = To do, Doing
Priority = 1

In this case, the following combinations will be synced:

1) Task with the To do status and priority 1

2) Task with the Doing status and priority 1

3) Issue with the To do status and priority 1

4) Issue with the Doing status and priority 1


5. Press Publish to save the connection.

You can also use these hotkeys to publish a connection:

  • Ctrl+S on Windows or Linux
  • Cmd+S on Mac
Changes in existing connections will not be applied before you update the issue. Please make sure to update the issue, if you want to apply changes.



What's next?

Add Field Mapping

See also

Initiate a Connection in Visual Mode


Have more questions? Ask the community




Back to How to Set up a Connection in Exalate Visual Mode