Ticketing & ITSM

Jira

Search, create, transition, and assign Jira issues from natural-language requests.

The dedicated Jira issue-management integration: Dex connects to Jira Cloud over the REST API v3 using Basic auth (a service account's email + API token) and runs the full ticket lifecycle in natural language — JQL search via /rest/api/3/search, issue creation, field updates, workflow transitions, ADF comments, and accountId-based assignment. Distinct from the OAuth-based Atlassian (Jira & Confluence) integration, which acts as the authorizing admin; this one acts as a fixed service account and covers Jira only.

Book a Demo

What Dex does with Jira

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (CoAdmin)

Search issues with JQL via GET /rest/api/3/search — by project, status, reporter, assignee, priority, labels, free text (text ~ "..."), with field selection and paging
Create issues via POST /rest/api/3/issue — Dex checks createmeta first so project, issue type, and required fields are valid before submitting
Update issue fields via PUT /rest/api/3/issue/{key} with patch semantics — only the fields you name change; clearing a field sets it to null or []
Transition issues through any workflow — Dex discovers the legal transitions per issue (GET /issue/{key}/transitions) and supplies required fields like resolution when closing
Add comments in Atlassian Document Format via POST /rest/api/3/issue/{key}/comment, including role-restricted visibility (e.g. Administrators only)
Assign or unassign via PUT /rest/api/3/issue/{key}/assignee — Dex resolves people to accountIds with /user/assignable/search first (GDPR-safe, no usernames)
List projects (GET /rest/api/3/project), components, versions, and users for routing and metadata lookups

For employees (self-service)

Find the Jira tickets you reported — Dex resolves your email to your accountId and scopes every query to reporter = you
Check the status and latest updates of one of your tickets ("PROJ-123 is In Progress, last updated 2 hours ago")
Read the description and comment thread of a ticket you reported
Add a comment to your own ticket — Dex confirms the text first and attributes it to you in the body
Transition your own ticket (resolve, reopen, cancel) — Dex shows you the allowed transitions for its current workflow state

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Search Jira for all unresolved issues in project OPS with priority Highest or High, ordered by last update
>Create a Task in project IT: "Replace failing switch in rack B4", priority High, labels it-ops and prod-incident, assigned to jane.doe@acme.com
>Transition PROJ-482 to Done with resolution "Done" and add a comment summarising the fix
>Reassign every open issue assigned to bob@acme.com in project PROJ to the project default assignee
>Delete PROJ-991 — it's a duplicate of PROJ-987 (Dex will confirm before deleting and mention the 14-day soft-delete window)

Employee prompts

>What Jira tickets do I have open?
>What's the status of PROJ-123?
>Add a comment to PROJ-118: "Still happening after the reboot, screenshots attached in email"
>Resolve my ticket PROJ-130 — the issue is fixed

Policy actions

Every action Dex can take on Jira is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`jira_list_issues`	Search and list issues with JQL via GET /rest/api/3/search	—
`jira_create_issue`	Create a new issue via POST /rest/api/3/issue (admin-side only — end-user self-service never files tickets)	—
`jira_update_issue`	Update issue fields (summary, priority, labels, …) via PUT /rest/api/3/issue/{issueKey}	—
`jira_transition_issue`	Move an issue through its workflow via POST /rest/api/3/issue/{issueKey}/transitions	self-only
`jira_comment_issue`	Add an ADF comment via POST /rest/api/3/issue/{issueKey}/comment	self-only
`jira_assign_issue`	Assign, unassign, or auto-assign an issue via PUT /rest/api/3/issue/{issueKey}/assignee	—
`jira_delete_issue`	Permanently delete an issue via DELETE /rest/api/3/issue/{issueKey} (14-day soft delete; Dex always confirms first)	approval
`jira_list_projects`	List projects and their metadata via GET /rest/api/3/project	—
`jira_list_users`	Look up users and resolve accountIds via GET /rest/api/3/user endpoints	—

How to configure Jira

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
Create (or pick) an Atlassian service account for Dex and make sure it's a member of your Jira Cloud site with the project permissions Dex needs (Browse Projects, Create Issues, Edit Issues, Transition Issues, Add Comments — Delete Issues only if you'll allow deletion).
2
Signed in as that account, go to id.atlassian.com → Account settings → Security → API tokens (https://id.atlassian.com/manage-profile/security/api-tokens) and create an API token. Copy it — it's shown once.
3
Note your Jira Cloud site URL in the form https://yourcompany.atlassian.net — no trailing slash, no /jira path. Jira Server / Data Center is not supported.
4
In Dex, enable the Jira integration and enter the site URL, the service account email, and the API token.
5
Dex validates the connection with a live GET /rest/api/3/myself call and confirms which account it's acting as — every API call from then on executes as that service account.

Credentials required

site_url: Your Jira Cloud site URL, e.g. https://yourcompany.atlassian.net (no trailing slash, no /jira path)
email: The Atlassian account email that issued the API token (typically a dedicated service / bot account)
api_token: API token created at id.atlassian.com → Security → API tokens for the service account (shown once)

Requirements

•Jira Cloud only — site URL must match https://<your-site>.atlassian.net; Server / Data Center is not supported by this connection
•All actions run as the service account: changes appear under its name, and currentUser() in JQL resolves to it, not the requesting employee — Dex scopes end-user queries by accountId instead
•The service account needs per-project permissions (Browse, Create, Edit, Transition, Add Comments, Delete are separate Jira permissions); a 403/404 usually means one is missing
•Rich-text fields (descriptions, comments) use Atlassian Document Format JSON — Dex composes ADF automatically
•Rate limits: ~10 req/sec sustained on Jira Cloud — Dex honors Retry-After on 429s and prefers JQL search over per-issue GETs for bulk reads

Related integrations

See Dex run Jira

Book a 30-minute walkthrough with our team and see how autonomous IT works in your environment — or get started for free.

Book a Demo Browse all integrations →