Back to docs

Jira Sync documentation

Overview

Jira Sync connects customer context in Attio with engineering work in Jira Cloud. Teams can create or link issues from records, work with selected records in bulk, automate issue creation and linking in workflows, and view current Jira details without leaving Attio.

Linked issues retain an Attio backlink. Jira update and comment webhooks keep stored issue details and unread-comment indicators current, while opening a widget refreshes issue details directly from Jira.

Connect Jira Cloud

  1. Install Jira Sync in the Attio workspace.
  2. Open the app's Connections tab and connect Jira Cloud.
  3. Approve the Jira issue, user, and webhook OAuth permissions.
  4. Open Settings and choose the Jira site, project, issue type, and optional priority.
  5. Use Check connection to validate access and create or renew dynamic Jira webhooks.

Create and link issues

Open an Attio record action to create a new Jira issue or link an existing one. Bulk actions apply the same operation to selected records. Created and linked issues appear in the Linked Jira issues widget with their summary, status, priority, assignee, last update, comments, and links to other affected Attio records.

The description accepts localized free text and Attio record variables. Leave it empty to use the default Attio context, or insert variables such as the record name, URL, and object fields. Variables are replaced with values for each target record.

Comments and issue changes

From a linked issue, Attio users can edit supported Jira fields and view or add comments. Comments added from Attio include the contributor's Attio email for attribution because Jira records the connected workspace account as the technical author.

Jira comment webhooks add a new-comment indicator for each Attio user. Opening the comment thread marks the current comments as seen. Users can edit or delete only comments they originally added through Attio.

Workflows

Jira Sync provides Create Jira issue and Link Jira issue workflow blocks. Both blocks accept values from a trigger or an earlier block and expose the resulting Jira issue ID, key, URL, summary, status, priority, project, issue type, and cloud ID to downstream steps.

Create and optionally link an issue

  1. Add the Create Jira issue block after a workflow trigger.
  2. Select the Jira project and issue type, then provide a summary.
  3. Optionally add workflow variables to the summary and description.
  4. To link the new issue, select Record to link and choose a record from the trigger or an earlier block. Jira Sync detects its object type automatically.
  5. Leave Record to link empty when the workflow should create a standalone Jira issue.

Workflows configured with the earlier target record type field should be reopened, checked, and republished after updating Jira Sync.

Link an existing issue

Use the Link Jira issue block when the Jira issue already exists. Select the Attio record and choose or supply the Jira issue from an earlier workflow value.

Deleted and resolved issues

By default, a Jira deletion webhook removes the deleted issue from every linked Attio record. Admins can turn this off to keep an unavailable placeholder until a user manually unlinks it.

Admins can optionally create a native Attio follow-up task for every linked record when Jira moves an issue into the Done status category. Repeated webhook deliveries are deduplicated.

Subscription and account size

Every workspace receives a 14-day free trial with unlimited users. Paid plans include the same feature set and are selected according to the total number of Attio workspace members. If the workspace grows beyond its plan, Jira write actions and workflow steps pause until an admin selects a larger plan.

View the Jira Sync pricing page.