Jira

Category: Issue Tracking
Connect by: Connect with OAuth
Official API docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

What the agent can see

Capability	API call	Risk	Needs approval
Search issues with a JQL query, most recently created first. (docs)	GET /search/jql	🟢 low	— no
Retrieve a single issue by ID or key. (docs)	GET /issue/{issueIdOrKey}	🟢 low	— no
List the comments on an issue. (docs)	GET /issue/{issueIdOrKey}/comment	🟢 low	— no

What the agent can do

Capability	API call	Risk	Needs approval
Create a new issue in a project (project, summary, issue type). (docs)	POST /issue	🟡 medium	✅ yes
Add a comment to an issue (plain text wrapped in Atlassian Document Format). (docs)	POST /issue/{issueIdOrKey}/comment	🟡 medium	✅ yes
Transition an issue to a new status by transition id. (docs)	POST /issue/{issueIdOrKey}/transitions	🟡 medium	✅ yes
Assign an issue to a user by accountId. (docs)	PUT /issue/{issueIdOrKey}/assignee	🟢 low	— no

Connecting it

• You provide: Atlassian account (OAuth)
• Where to get it: Create an OAuth 2.0 (3LO) app at the Atlassian developer console (developer.atlassian.com), configure the callback + scopes, then consent at auth.atlassian.com; the connector resolves your site's cloudId via accessible-resources.
• Permissions/scopes: read:jira-work, write:jira-work, read:jira-user, offline_access

Account setup

• Account needed: A Jira Cloud site (jira.atlassian.net).
• App registration: OAuth 2.0 (3LO) app in the Atlassian developer console with scopes read:jira-work, write:jira-work, read:jira-user; the callback resolves cloudId from accessible-resources.
• Verification required: Marketplace review only for publicly distributed apps; a private/own-use 3LO app needs no review.
• Testing: Use a free Jira Cloud site; comment bodies must be Atlassian Document Format (ADF).

Limits

Atlassian applies cost-based REST rate limiting; HTTP 429 with Retry-After on exceed.