Search, create, and move Jira issues, comment on them, list projects, and pull issue attachments into your workflows.
| Category | 🐙 Development |
| Connection | ⚡ OAuth 2.0 one-click, handled by Nango |
| Actions | 6 total — 3 read, 3 write |
Once connected, Jira exposes the following actions. The AI can call them with #-mentions in chat, an agent can be granted a subset as tools, and a workflow can run them in an integration-action node.
| Action | Type | What it does | Proxy |
|---|---|---|---|
Search Issuessearch-issues | Read | Search Jira issues by JQL or text. | — |
Create Issuecreate-issue | Write | Create a new Jira issue. | — |
Transition Issuetransition-issue | Write | Move a Jira issue to a new workflow status. | — |
Add Commentadd-comment | Write | Add a comment to a Jira issue. | — |
List Projectslist-projects | Read | List Jira projects the user can access. | — |
Get Attachmentget-attachment | Read | Download a single Jira issue attachment by ID. | Yes |
Actions tagged Write create, update, or delete data. In chat and agent paths they pause for your confirmation before running; workflows treat their deterministic wiring as implicit consent. Agent tools covers how to scope which actions an agent may use.
Jira is governed per organization: an admin sets a monetary spend cap and a monthly call quota. A quota of 0 disables the integration — it never means unlimited. See the Integrations overview for the full governance model.