Jira integration¶

Connect DXDT to Jira Cloud with read-only access so the platform can search and read issues, projects, and statuses for incident correlation and triage. DXDT is configured to read only.


Setup time	~8 minutes
Difficulty	Easy

Access required: Atlassian account with read access to the relevant Jira projects

Prerequisites¶

An Atlassian Cloud account that can log in to your Jira site
Browse-project (read) access to the Jira projects DXDT should query
Your Jira domain, e.g. yoursite.atlassian.net

Setup¶

1. Choose a least-privilege Atlassian user¶

A Jira API token inherits the full permissions of the user who creates it. Use (or create) a user limited to browse/read access on the relevant projects, and avoid admin accounts so DXDT stays read-only in practice.

Note

The token can do anything the user can, so scope the user tightly.

2. Create an API token¶

Sign in as that user and open https://id.atlassian.com/manage-profile/security/api-tokens. Click Create API token, label it DXDT Jira, and copy the value immediately — it is shown only once.

Open id.atlassian.com/manage-profile/security/api-tokens
Click Create API token
Label it DXDT Jira and copy the token

3. Identify your domain and email¶

Your email is the Atlassian login email of that user. Your domain is your Jira host, either the slug yoursite or the full URL https://yoursite.atlassian.net.

Note

DXDT expands a bare slug to https://<slug>.atlassian.net automatically.

4. Enter the values in DXDT¶

In the plugin Configuration tab, paste Domain, Email, and API Token and save. DXDT validates with a read-only ping.

Configuration fields¶

Field	Where to find it
Email (`email`)	The Atlassian login email of the least-privilege user who created the token.
API Token (`api_token`)	The token from Create API token at `id.atlassian.com/manage-profile/security/api-tokens`.
Domain (`domain`)	Your Jira host — slug `yoursite` or full URL `https://yoursite.atlassian.net`.

Verify the connection¶

Save on the Configuration tab and confirm the Live Status panel reports healthy; DXDT runs a read-only ping and can then list projects.

Security

Credentials are stored encrypted per-tenant and used only for read-only Jira calls.

Troubleshooting¶

401 Unauthorized

Mismatched email and api_token, or a mistyped/expired token. Regenerate the token and re-enter it alongside the exact owner login email.

JQL search returns nothing

The token owner lacks Browse Projects permission on those projects. Grant browse/read access to the relevant projects or use a user that already has it.

Host not found

Wrong domain. Use the correct *.atlassian.net slug or full URL.

Vendor documentation: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/