This page covers the integration settings that apply when Jira is one side of a connection.
Use it when you're configuring a relationship that includes Jira. Which settings appear depends on whether your Jira organisation is the source or the target.
Connecting Jira
Jira connects through an authorisation flow rather than entered API keys. Use Connect to Jira to authorise, then, if your account has more than one Jira site, choose the site to connect when prompted. Once connected, the site, URL, and connected user are shown.
Project and issue type
Project: the Jira project tickets sync to, identified by its project key.
Issue type: the issue type applied to synced tickets. Required on both sides.
Comments
Sync public comments and Sync internal comments: which comment types sync. For Jira Service Management projects, at least one must be selected.
Sync filter and reverse sync
Sync filter (source): which tickets to sync:
All,By assignee,By queue, orBy organisation, with the specific value selected below.Reverse sync (target): send updates back, filtered
By assignee,By queue, orBy organisation.
Source vs target: As the source, you set the sync filter that selects which Jira tickets sync. As the target, reverse sync with its assignee, queue, or organisation filter becomes available. The queue and organisation filters apply to Jira Service Management projects.
The API configuration override at the bottom of the form works the same on every platform. See Integration configuration for how it works.
Related pages
Integration configuration: shared settings and the API override.
Jira integration setup guide: connecting Jira to Support Fusion.