Jira Connectors

The Jira Connectors page lets system administrators configure connections between Fusion Online and Atlassian Jira Cloud sites. Each connector defines how Fusion Online communicates with Jira and what data is synchronized by default.

Most organizations only need a single connector. You can create additional connectors if you manage projects in multiple Jira sites or need different default sync configurations.

For an overview of how Jira synchronization works end-to-end, see Concepts → Jira integration

Creating a connector

  1. Navigate to Setup → Jira Connectors.

  2. Click + create new Jira Connector.

  3. Enter a name for the connector (for example, Corporate Jira Cloud) and click Save.

  4. Click Authorize with Atlassian to sign in to Jira.

  5. You’ll be prompted to approve Fusion Online as a connected app using Atlassian’s OAuth (3LO) authorization flow.

  6. Once authorized, select the Jira site that this connector will access.

Sync options

After authorization, you can configure default sync options that define what data will be pulled from Jira or pushed to Jira by default for any project using this connector.

Many of the fields used in Jira synchronization rely on Jira custom fields. These can be created either system-wide (available to all projects) or per-project in Jira. When configuring sync options in Fusion Online, you can select from either type.

Pull options

Select which Jira fields will be imported into Fusion tasks:

  • Task Status – maps Jira status category (To Do / In Progress / Done) to Fusion task states.

    • To Do → Not Started

    • In Progress → Started

    • Done → Completed

    • If a Jira issue is in a Done state but still has a remaining estimate, Fusion will still set the remaining duration to zero and mark the task as Completed.

    • Fusion enforces a consistent relationship between task state and duration values, while Jira does not, so status always takes precedence when synchronizing.

  • Duration – uses Jira’s Time Tracking fields to update Fusion task duration.

    • Fusion reads both the Original estimate and Remaining estimate fields from the Jira issue.

    • When the task is Not Started, Fusion uses the Original estimate (if set); if it is not set, it uses the Remaining estimate.

    • Once the task has Started, Fusion uses the Remaining estimate.

    • If no durations are defined in Jira, Fusion will not change the task’s duration values — except when marking a task as Completed, where the remaining duration is automatically set to zero.

  • Low-risk Duration Ratio – optional mapping that determines how Fusion calculates the low-risk duration relative to the focus duration.

    • If this mapping is not configured, or the Jira field has no value, Fusion keeps the ratio that already exists on the task (usually 2× by default).

    • When mapped to a Jira number field, the numeric value is used directly as the ratio.

    • When mapped to a selection list, Fusion looks for a numeric value or pattern such as 2X, 3X, etc.

    • Ratios less than 1 are ignored.

  • Status Comments – map to a Jira text field for importing comments.

Push options

Select which Fusion task fields will be exported to Jira:

  • Criticality – Jira text field.

  • Criticality Ratio – Jira number or text field.

  • Days Until Critical – Jira number or text field.

  • Projected Start – Jira date field.

  • Last Sync Date – Jira date field.

  • Fusion Task URL – Jira URL field (link back to the task in Fusion Online).

Managing connectors

  • Edit – open an existing connector to re-authorize or adjust default options.

  • Delete – removes the connector and its configuration (projects using it will lose their Jira connection).

  • Projects tab – displays a list of Fusion projects linked to this connector.

  • History tab – view a log of recent synchronization operations run under this connector.

Deleting a connector does not delete linked Jira data, but projects using it will no longer be able to perform Pull or Push actions until re-associated with another connector.

Permissions and authorization

Each connector uses Atlassian 3LO authorization tied to the user who authorized it. Later, when a project manager performs a Pull or Push, their own Jira authorization will be used for that sync operation.

Sync operations always run using the Jira account of the user who initiates them. Jira permissions of that user determine which issues can be read or updated.

See also

Last updated

Was this helpful?