Skip to content

guides

Intended Documentation

Jira Connector Setup (Beta)

Connect Intended to Jira. Create an Atlassian API token, paste your Jira base URL, account email, and token, and run Test connection. HTTP Basic (email:apiToken) over HTTPS. Beta until validated against your live Jira site.

intermediate3 min readpartial
PartialSource: codeValidated: 2026-07-09

Jira Connector Setup (Beta)#

Connect Intended to Jira so approved intents can create issues (optionally with a first comment) through the real Jira adapter (packages/execution-engine/src/adapters/jira.ts). Every write is Authority-Token-verified and ESCALATEs for approval under the starter policy.

This connector is Beta

The adapter is real and covered by hermetic (mocked-HTTP) tests that pass in CI with no live tenant. Live proof against your real Jira site is pending — treat Jira as Beta, not GA. See the Capability Truth Matrix.

What the adapter does#

PropertyValue
Actionsjira.issue.create (creating an issue; a comment is posted as a follow-on when payload.comment is set)
AuthHTTP Basic — Authorization: Basic base64(<email>:<apiToken>)
Host validationHTTPS required; embedded credentials rejected. Note: the adapter does not pin an *.atlassian.net suffix — any HTTPS baseUrl you configure is accepted, so make sure you enter your real Jira site URL
Test connectionGET /rest/api/3/myself

On the comment capability

The manifest lists jira.issue.comment, but in the adapter commenting only happens as an optional follow-on to jira.issue.create (when the intent payload includes a comment). There is no standalone comment-only action path today.

Provider-side steps#

1. Base URL (baseUrl, required)#

Your Jira site, e.g. https://your-org.atlassian.net. Enter your exact site URL (the adapter accepts any HTTPS host, so a typo won't be caught by a domain pin).

2. Account email (email, required)#

The Atlassian account email the API token belongs to, e.g. ops@your-org.com. Use a dedicated integration/service account.

3. API token (apiToken, required)#

  1. Sign in as the integration account and go to id.atlassian.com → Security → Create and manage API tokens.
  2. Click Create API token, label it (e.g. intended-connector), and copy the value once.
  3. It is combined with the email as HTTP Basic auth.

Least-privilege scope guidance#

  • Matrix scopes for this connector: read:jira-work, write:jira-work.
  • Atlassian API tokens inherit the account's project permissions. Constrain the integration account to only the target project(s), with Create Issues and Add Comments permissions — not Jira administration.
  • Do not use a Jira-admin or site-admin account for the token.

Fields to paste into the connect dialog#

Open Connectors → Connect a system → Jira → Configure auth:

Field labelKeyRequiredValue
Jira Base URLbaseUrlYeshttps://your-org.atlassian.net
Account EmailemailYesops@your-org.com
API TokenapiTokenYesYour Atlassian API token

Credentials are stored per-tenant, AES-256-GCM-encrypted, and never displayed back.

Run Test connection#

  1. Finish the connect wizard to store the credential.
  2. On the connector card, click Test connection.
  3. The adapter calls GET /rest/api/3/myself. A green result means the email + token Basic auth is valid against your site.

Next steps#

Jira Connector Setup (Beta) | Intended