Jira sync#

If a project is linked to Jira, you can mirror its Jira issues onto the board. Each Jira issue becomes a card, placed in the column that matches its status.

Before you start#

The team must have connected Jira — see the Jira integration guide. Once it has, the board's Jira sync controls appear; you pick which Jira project to sync from the dialog itself (next section).

Enable sync#

Owners and admins turn sync on:

1. Open the board and click Jira sync.
2. Pick the Jira project from the dropdown — this lists every project your connected Jira account can see. (It's the project's shared Jira link, so it's also what flow nodes reference.)
3. Flip Sync cards from Jira on.

Columns mirror your Jira board#

You don't set columns up by hand. The sync reads your Jira board's own column layout (e.g. Backlog · Paused · Refinement · In Progress · In Test · Completed) and recreates those columns on the portal board, then files each issue into the column its Jira status belongs to — exactly as Jira groups them.

This uses the Jira board configuration, not the raw workflow statuses, so:

• Column names match what you see in Jira (in Jira's language).
• A column like In Test that groups several underlying statuses just works — every issue in those statuses lands in In Test.

So a board synced against a Jira project ends up mirroring that Jira board's columns automatically.

Refining the mapping (optional)#

If you'd rather collapse several Jira statuses into one column — say map both In Review and In Progress to a single In Progress column — open the Jira sync dialog and add those status names to the column. A status that's mapped somewhere won't get its own auto-created column on the next sync.

Run a sync#

Anyone who is a developer or above can click Sync now. A progress panel shows each step as it runs — first Setup (reading the Jira workflow and counting issues), then one step per column as it loads, e.g. Loading Backlog, Loading In Progress, Loading Done — each with a live count.

Each sync:

• Adds a card for every Jira issue that doesn't have one yet.
• Updates existing mirrored cards (title, priority, link) and moves them if their status now maps to a different column.
• Leaves your native cards — the ones you created on the board — untouched.

It loads the project's issues column by column, paging through all of them, so the whole project is mirrored — not just the most recent issues. Mirrored cards show the Jira issue key; click it to open the issue in Jira.

Good to know#

• Assignees aren't mapped. A Jira assignee isn't a portal user, so mirrored cards stay unassigned. You can still assign them to a project member on the board.
• It's a manual sync. There are no webhooks — you sync on demand. Counts in the progress panel are Jira's approximate totals, so they may be off by a little.
• Nothing is deleted. Cards for issues that no longer come back from Jira are kept, not removed.
• Disable any time. Turning sync off leaves the existing cards on the board; they just stop updating.