> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thread.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> Connect Jira so guides can verify outcomes against live project status and agents can read, create, and update issues.

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](/guides/outcomes-and-verification).

**Milestone checks.** Motion milestone verification can consult Jira's read tools as evidence, like any connected connector. See [Milestones and verification](/motions/milestones-and-verification).

**Agent tools.** Agents in Motions and workflows get a scoped Jira toolset:

| Reads                                            | Writes (approval-gated)                   |
| ------------------------------------------------ | ----------------------------------------- |
| Get an issue, search with JQL                    | Create an issue                           |
| Read comments                                    | Update an issue, add a comment            |
| List projects, issue types, statuses, priorities | Transition an issue through your workflow |
| Look up users and assignable users               |                                           |

Writes follow per-action autonomy like everything else an agent does — actions you haven't opted out of approval for land in your [Inbox](/inbox/overview) first.

## Connect Jira

<Steps>
  <Step title="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.
  </Step>

  <Step title="Confirm the site">
    Back in Thread, the connector page shows the connected site's name and URL. One Jira site per
    organization.
  </Step>

  <Step title="Test the connection">
    Use **Test Connection** on the connector page to confirm reads work end to end.
  </Step>
</Steps>

## 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

<AccordionGroup>
  <Accordion title="Connect fails or loops back">
    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.
  </Accordion>

  <Accordion title="A guide's Jira check finds nothing">
    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.
  </Accordion>

  <Accordion title="Agent can't transition an issue">
    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.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Outcomes and verification" icon="badge-check" href="/guides/outcomes-and-verification">
    How a Jira read closes a guide's outcome.
  </Card>

  <Card title="Motion agents" icon="robot" href="/motions/agents">
    Where Jira tools show up in agent runs and approvals.
  </Card>
</CardGroup>