Jira Connection

Connects your agent to Jira Cloud for project and issue tracking. Full read access to issues, sprints, boards, and projects. Write operations (create/update issues, add comments, transition status) require confirmation.

Authentication

API token (recommended) or OAuth2.

• email — Atlassian account email
• api_token — API token from id.atlassian.com/manage-profile/security/api-tokens
• base_url — Your Jira instance (e.g., https://company.atlassian.net)

Endpoints

Issues

• GET /rest/api/3/search — Search issues with JQL (Jira Query Language)
• GET /rest/api/3/issue/{key} — Get issue detail with all fields
• POST /rest/api/3/issue — Create issue (requires confirmation)
• PUT /rest/api/3/issue/{key} — Update issue fields (requires confirmation)
• POST /rest/api/3/issue/{key}/transitions — Transition issue status (requires confirmation)
• GET /rest/api/3/issue/{key}/changelog — Get issue change history

Comments

• GET /rest/api/3/issue/{key}/comment — List comments on an issue
• POST /rest/api/3/issue/{key}/comment — Add comment (requires confirmation)

Sprints

• GET /rest/agile/1.0/board/{id}/sprint — List sprints for a board
• GET /rest/agile/1.0/sprint/{id}/issue — Get issues in a sprint

Boards

• GET /rest/agile/1.0/board — List boards
• GET /rest/agile/1.0/board/{id}/configuration — Get board columns and filters

Projects

• GET /rest/api/3/project — List projects
• GET /rest/api/3/project/{key} — Get project detail

Rules

• Rate limit: follows Atlassian cloud rate limits (varies, typically 100/10s)
• JQL queries are constructed by the agent from natural language — reviewed before execution
• Issue creation and status transitions always require confirmation
• Bulk issue operations (>5) require itemized confirmation
• All write operations logged to audit trail