Keep a board in step with Jira, Azure Boards, Trello, Linear or GitHub Issues

Connect a board to one Jira project, Azure Boards area, Trello board, Linear team or GitHub repository, map the fields, and changes move both ways - nothing is ever deleted on either side.

In short

Two-way sync keeps a board in step with one Jira project or one Azure Boards area. Title and status always move both ways; you choose the other fields - description, type, assignee, priority, estimate, labels and parent. Each card shows its Jira or Azure key and a link to open it there.

Before you start

• First: an organization admin connects Jira or Azure Boards once, in Organization settings, under Connections - see /help/settings/connect-jira-cloud, /help/settings/connect-jira-data-center or /help/settings/connect-azure-boards. The board picks that connection; nobody types a token here.
• The connection's account must be allowed to create, edit and move issues in the project.
• Who: you manage the board ("Create and manage boards").
• Plan: two-way sync is on a paid plan, and the plan sets how many boards you may keep in step (see Plan & usage). A one-time import works on every plan.

Steps

1. Open Board settings › "Connections" and press "Set up" on "Trackers". Press "Connect a work tracker".
2. Under "Connection", choose one of the organization's tracker connections, then type the "Project": a key such as SHOP for Jira, the project name for Azure Boards. For Azure Boards, "Area path" and "Iteration path" narrow it if you want.
3. Press "Test connection" and wait for "Connected to SHOP.", then press "Save and map fields".
4. Under "Fields kept in step", choose the fields. Under "Status and column", give each tracker status a column, and match types and priorities.
5. Press "Save and start sync".
6. Read the summary: it names the connection the sync goes through. Its site, token and webhook stay in Organization settings, under Connections - there is nothing to copy here.

Result: the summary says, for example, "Jira Cloud · SHOP · 42 cards in step", with "Last read" and "Next read".

Good to know

• When both sides changed a field, the later change wins, and the card's history keeps both values. Tick "Only conflicts" in the sync log to see every such field and which side won.
• In the mapping, each kept field has "Which way it goes": "Both ways", "Only from the tracker" (the tracker always wins; a change on the board is not sent) or "Only to the tracker" (the board always wins; a change in the tracker is overwritten by the board's value).
• Nothing is deleted on either side. An item removed in the tracker marks its card "Removed in Jira - this card is kept."
• Comments and attachments are not synced in this version.
• Assignees match by a confirmed email of a workspace member; anyone else stays unassigned.
• Tick "Make a work item for each new card made on this board" to send new cards to the tracker too.
• Without the webhook the board reads the tracker every few minutes. "Sync now" reads within half a minute.
• Changes are made as the person who saved the connection or started the sync. A locked card takes nothing.
• Two-way sync is on a paid plan. A one-time import works on every plan. See /help/boards/import-cards.
• "Disconnect" stops this board's sync at once; the organization's connection stays for other boards. Cards keep their keys, so searching a key still finds them.
• What happens next: cards show their Jira or Azure key and a link. "Sync log" lists every change, and "Disconnect" ends the sync at once.

Give the token only what it needs The token can change every issue its account can reach. Use an account that sees only the project you sync.

Details for your IT team

• The webhook belongs to the organization's connection, not to the board: its address and secret are made in the connection's wizard. See /help/settings/connect-jira-cloud and /help/settings/connect-azure-boards.
• A Jira Cloud site must end in atlassian.net. Other sites must be public https addresses.
• The webhook only names an item; {{brand}} reads the item again with the board's token, so a forged call changes nothing.

If something goes wrong

• "The connection did not work" - the message names the problem: the site, the token, the project, or missing rights.
• "A Jira Cloud site ends in atlassian.net."
• "Map at least one status to a column."
• A card shows "Not sent: ..." - the tracker refused the value; the reason says which. "Sync log" lists every change.
• The tracker answers "too many requests": the sync waits and tries again by itself.

Related

• /help/boards/import-cards
• /help/boards/board-webhooks-and-repositories
• /help/boards/card-keys