Skip to main content
For technical onboardings, the truth about “is it done” often lives in Jira. Connecting it gives Thread two things: a verification source — a guide can close an outcome on a fresh read of a pinned Jira project — and a working surface for agents, which can search issues, add comments, create tickets, and move them through your workflow.

​
What it powers

Guide verification. Attach the Jira tool to a guide and pin a project. The guide sees that project’s issues and their live status — and nothing outside it. When the guide believes the outcome is reached, it takes a fresh read of the project; the read lands in the watch log as a receipt. What “done” means stays in your instructions. See Outcomes and verification. Milestone checks. Motion milestone verification can consult Jira’s read tools as evidence, like any connected connector. See Milestones and verification. Agent tools. Agents in Motions and workflows get a scoped Jira toolset: Writes follow per-action autonomy like everything else an agent does — actions you haven’t opted out of approval for land in your Inbox first.

​
Connect Jira

1

Open Connectors → Jira → Connect

In Thread, go to Connectors → Jira and click Connect. You’ll be sent to Atlassian to sign in and approve access (standard Atlassian OAuth). Choose the Jira site you want Thread to use.
2

Confirm the site

Back in Thread, the connector page shows the connected site’s name and URL. One Jira site per organization.
3

Test the connection

Use Test Connection on the connector page to confirm reads work end to end.

​
Scope

The connection’s own scope is the guardrail:
  • A guide’s Jira tool is bound to the project you pin when attaching it — it reads that project’s issues and nothing else. Even if an issue is moved, Thread re-verifies that what it read belongs to the pinned project.
  • Agent tools operate with the access of the connected Atlassian account — Jira’s own permission model applies to every read and write.

​
Troubleshooting

Make sure you approved access for the right Atlassian site, and that the account you signed in with has access to it. Reconnecting from Connectors → Jira issues fresh tokens.
Confirm the right project is pinned on the guide’s Jira tool row, and that the connected account can see the project. The check reads live status — an issue in a different project never counts.
Transitions are defined by your Jira workflow — the target status must be reachable from the issue’s current status, and the connected account needs permission to make the move.

Outcomes and verification

How a Jira read closes a guide’s outcome.

Motion agents

Where Jira tools show up in agent runs and approvals.