Cotool + Jira
Connect Jira to Cotool so agents search with JQL, create and update security issues, raise Jira Service Management alerts, and start from Jira events.
The short answer
The Jira integration lets Cotool agents work with Jira Cloud issues: search with JQL, read details and history, create and update issues, comment, change status, and move files between Jira and the agent's sandbox. Jira webhooks and Automation rules can also start agents or create Cotool alerts.[1]
How it connects: Connect with OAuth as a user, or with an Atlassian service account, which is not associated with a person and so survives employee offboarding.[1][5]
What Cotool uses from Jira
Response actions
These change state in Jira, so they are the steps teams usually gate behind approval.
- Create and update issues
- Agents create issues, including in projects with required custom fields, which they discover with a create-field metadata tool first, and update, comment on, and transition them.[1]
- Raise a Jira Service Management alert
- Agents can create a JSM Ops alert and optionally notify a user, team, escalation policy, or on-call schedule.[1]
Detections, hunts, and triage
- Triage from a Jira ticketTriage
- A Jira webhook or Automation rule starts a response agent when a security issue is created. Cotool's docs show an agent that, given a ticket ID, fetches alert details from SentinelOne, searches Splunk, checks indicators in VirusTotal, and updates the Jira ticket with findings.[1][2][6]
- Insider risk from Jira issuesResponse
- Cotool's Respond page shows an Insider Risk Responder fed by Jira security issues.[3]
Setup and permissions
For a service account, give it Jira product access, add it to the right projects, and create an OAuth 2.0 credential with the scopes listed here. Project permissions alone are not enough; Jira rejects writes without product access.[1][5]
| Permission | Access | Why |
|---|---|---|
read:jira-workView Jira issue data.[4] | Read | View Jira issue data.[4] |
read:jira-userView user profiles.[4] | Read | View user profiles.[4] |
write:jira-workCreate and manage issues.[4] | Write | Create and manage issues.[4] |
How Cotool works with Jira
- An OAuth connection uses the authorizing user's Jira access and stops working if that user is deactivated. A service account avoids that because it is a non-human Atlassian identity.[1]
- Jira triggers create a Cotool alert for each event by default; turning off Create alert runs the agent directly.[1]
FAQ
- Can an agent create issues in projects with required custom fields?
- Yes. Cotool's Jira tools include a field-metadata lookup that lists required fields, IDs, types, and allowed values before an issue is created.[1]
Sources
- Jira integration (Cotool docs) · accessed November 16, 2026
- Creating agents from chat (Cotool docs) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Jira scopes for OAuth 2.0 (3LO) and Forge apps (Atlassian Developer) · accessed November 16, 2026
- Understand service accounts (Atlassian Support) · accessed November 16, 2026
- Jira automation triggers (Atlassian Support) · accessed November 16, 2026
- Issue search REST API (Atlassian Developer) · accessed November 16, 2026
