Jira integration

Fusion Online can integrate directly with Atlassian Jira Cloud to synchronize task and project data between the two systems. This integration lets you keep task information aligned without manually updating both tools. Team members can update work in Jira while project managers maintain schedule data in Fusion Online.

This initial release focuses on direct synchronization between existing Fusion tasks and Jira issues, providing a foundation for deeper integration in future versions.

Before you begin

To use Jira integration, you’ll need:

A Jira Cloud site where you have project access.
A Fusion Online Jira Connector configured by a system administrator.
Atlassian authorization — both the connector administrator and any user who performs a Pull or Push will need to authorize Fusion Online to access Jira on their behalf.
Permissions in Jira for any issues you plan to sync.

Fusion Online does not use impersonation or delegation when synchronizing with Jira. Each sync (Pull or Push) runs using the Jira account of the user who clicked the button. That user must have sufficient Jira permissions to read or update the linked issues.

Current limitations

This initial version of the Jira integration supports direct linking between existing Fusion tasks and existing Jira issues. It does not yet include the ability to:

Create new tasks or issues automatically in either system during sync.
Roll up data such as status or duration from Jira sub-tasks or epic issues to higher-level tasks.

These capabilities are being considered for future releases. If your workflows would benefit from them, we’d appreciate hearing your use cases and feedback — please share them with the Fusion Online product team through your usual support channel.

Overview of Jira sync

Jira integration connects Fusion Online projects and tasks with Jira projects and issues. You can choose which data to synchronize in each direction.

Create a Jira connector – define connection details and default sync options.
Associate a connector with a project – link the Fusion project to one or more Jira projects.
Link tasks – assign a Jira Task Key to each Fusion task.
Sync data – initiate a Pull (import from Jira) or Push (export to Jira).

Step 1 – Create a Jira connector

Administrators can create one or more Jira connectors from Setup → Jira Connectors.

Each connector defines:

The Jira site it connects to.
The default sync options — which data fields to pull or push.

You can create multiple connectors if you need to connect to different Jira sites or use different default sync configurations for various projects.

Most organizations only need a single Jira Connector, but multiple connectors are supported for advanced configurations.

Step 2 – Associate a connector with a project

Open Project Details for a Fusion project and locate the Jira connector item in top-right action menu.

Here you can:

Select a Jira Connector.
Choose one or more Jira projects authorized for synchronization.
Optionally override the default sync options defined by the connector.

Once a connector is associated, you’ll see Pull and Push buttons in the Jira Integration section on the Project Details screen.

Step 3 – Link tasks to Jira issues

After a project is connected, each task in the project displays a new field called Jira Task Key on the Task Details screen.

You can:

Enter the Jira issue key directly (e.g., PROJ-123).
Search by issue name or key within the Jira projects authorized for this Fusion project.

This links the Fusion task with the corresponding Jira issue for syncing.

Step 4 – Sync data between Fusion and Jira

When tasks are linked, you can click Pull or Push on the Project Details page to start synchronization.

Pull (import from Jira → Fusion)

Pull updates Fusion task data from Jira fields:

Field

Description

Task Status

Uses the Jira issue’s state category (To Do, In Progress, Done) to set the Fusion task status (Not Started, Started, Completed).

Duration

Pulls from Jira Time Tracking and updates Fusion task duration.

Low-risk Duration Ratio

If mapped, multiplies the pulled duration by the specified ratio (e.g., 2X, 3X) to calculate the low-risk duration for the Fusion task.

Status Comments

If mapped, copies text from a Jira custom field into Fusion’s Status Comments.

If “Use low-risk duration ratio” is not selected, Fusion keeps the existing ratio (default 2×).

Push (export from Fusion → Jira)

Push sends selected Fusion task data to Jira custom fields:

Field

Description

Criticality

Writes to a Jira text field.

Criticality Ratio

Writes to a Jira number or text field.

Days Until Critical

Writes to a Jira number or text field.

Projected Start

Writes to a Jira date field.

Last Sync Date

Writes to a Jira date field.

Fusion Task URL

Writes a direct link to the Fusion task in a Jira URL field.

After each sync, you can click the last Pull or Push date to view the sync history, including any warnings or errors.

Example workflow

Team members update task state, remaining duration, and status comments in Jira.
Before performing the next schedule update in Fusion, the project manager Pulls data from Jira.
After running the schedule update and recalculating critical chain metrics, the manager optionally Pushes results back to Jira — for example, Criticality or Projected Start.

This workflow keeps both systems aligned without duplicate manual entry.

Troubleshooting

Issue

Possible Cause

Resolution

No Jira sites appear when creating a connector

The authorized user does not have any Jira Cloud sites linked to their Atlassian account.

Ensure the user has access to a Jira Cloud site.

Pull or Push fails for some tasks

The user performing the sync lacks permission to view or update those Jira issues.

Ensure the syncing user has issue-level permissions in Jira.

Authorization expired

Atlassian 3LO tokens expire after a period of inactivity.

Click Authorize with Atlassian again in Fusion Online to refresh authorization.