🧭 Jira integration

Connect Jira once and every agent in your squad can work in it for you, with exactly as much access as you decide to give, and a receipt for every call it makes.

What your squad can do in Jira

• Look things up, fetch bulk issues; get all groups; get all issue type schemes, and more.
• Do real work, add attachment; add comment; add users to project role; add user to group, and more.
• Run it on a schedule: any of the 97 available tools below can be part of a scheduled task or a mission.

How to connect

1. In your dashboard, open Integrations and find Jira.
2. Click Connect and pick an access level (we recommend Read + write): this is the ceiling for every agent.
3. Sign in to Jira in the window that opens and approve. You land back on the Integrations page with the account live.

You can change an account's access level any time under Manage. It applies instantly, no re-authorization. If the connection ever expires, the card shows Reconnect; one click re-authorizes the same account with the same settings.

Multiple accounts: connect as many as you need (say, yours and a client's). One is primary. Agents use it unless a mission says otherwise.

Access levels

The level you pick at connect time is enforced on our side for every agent call: an agent can never do more than the level allows, no matter what it's asked.

On top of the connection's level, every agent can be individually allowed, scoped down, or denied for this app from the Integrations page. Deny an agent and it doesn't even see the connection.

Every tool, in plain terms

The 97 tools agents use in Jira through Mission Control, and the lowest access level that includes each. Agents discover these themselves. You never have to name a tool; asking in plain language is enough.

What agents can't do in Jira (yet)

• Anything not in the table above. The tools mirror what Jira makes available to connected apps. If Jira doesn't expose an operation, agents can't perform it either.
• If something you need is missing, there's usually a path: add the service's API key under Settings → Custom integrations and your agents can call it directly. See custom integrations & secrets. You can also ask your lead agent to open a ticket describing what it needs.

Using it in missions

Just ask in plain language: “check Jira for …”, “create … in Jira”, “every Monday, … ”, and the agent finds the right tool, runs it, and reports back with a receipt in your Runs ledger. Anything outward-facing (sending, posting, publishing) that a mission didn't clearly authorize comes back to you as a ticket first.

Troubleshooting