Farline AI for AtlassianFeatures

Syncing with Jira

Push mapped forecast values back to Jira epics and create missing epics when needed.

Jira Sync pushes forecast data back to Jira, keeping your Jira epics aligned with the plan you've built in Farline AI.

What Sync Does

When you trigger a sync, Farline AI updates the Jira fields you've configured in the Mapping tab for each matching epic in the selected scenario. It can also create new Jira epics for manual work items that do not already exist in Jira. After syncing:

  • Your Jira Roadmap view reflects the forecasted timeline
  • Epics can receive updated start date, target date, and size values if those mappings are configured
  • Stakeholders viewing Jira directly see an up-to-date delivery picture

Sync is one-directional: Farline AI pushes plan data to Jira. Changes made directly in Jira are not pulled back into Farline AI automatically.

Required Permission

Syncing requires the write:jira-work permission. This was requested at install time.

In plain terms: the app needs permission to update your Jira epics. If your site admin approved this permission when installing the app, the Sync button will be available. If it was not approved, contact your Jira site admin to update the app permissions.

How to Trigger a Sync

  1. Open your project plan in the Farline AI tab
  2. Click Sync to Jira
  3. Select the scenario you want to sync
  4. Review the mapped fields and any new epics that will be created
  5. Click Confirm Sync to apply the changes

The Sync to Jira confirmation screen

What Gets Updated

For each work item in your forecast:

Sync actionValue Written
Mapped start date fieldThe work item's forecasted start date
Mapped target date fieldThe work item's forecasted end date
Mapped size fieldThe work item's forecasted size
New Jira epicCreated when a work item does not already map to an existing epic

If no writable mappings are configured, the Sync button stays disabled until the Mapping tab is set up.

Conflict Behaviour

If a Jira epic already has mapped values set:

  • The mapped fields are overwritten by the forecast values
  • Other Jira fields are left untouched

If you want to preserve existing Jira values for specific epics, remove those work items from the scenario before syncing, or clear the relevant mapping.

Undoing a Sync

Sync does not create a restore point. If you need to revert changes after a sync:

  • Manually update the Jira fields again
  • Or run a sync from a different scenario with the dates you want