Overview
The Jira tools integrate with Atlassian Jira Cloud REST API v3 to help you manage project progress from your workflows. You can create, search, update, and transition issues, add comments, and discover projects.Key Features
JIRA_CREATE_ISSUE- Create an issue (task, story, bug, or sub-task) in a Jira project.
JIRA_GET_ISSUE- Fetch a single issue by its key (e.g.
PROJ-123) or numeric ID.
- Fetch a single issue by its key (e.g.
JIRA_SEARCH_ISSUES- Search issues with a JQL query using the enhanced
/search/jqlendpoint. Returns paginated results with anextPageToken.
- Search issues with a JQL query using the enhanced
JIRA_UPDATE_ISSUE- Update fields on an existing issue: summary, description, assignee, priority, and labels.
JIRA_TRANSITION_ISSUE- Move an issue to a new status (e.g. To Do → In Progress → Done), with an optional comment.
JIRA_ADD_COMMENT- Add a comment to an issue. Accepts plain text and converts it to Atlassian Document Format (ADF) automatically.
JIRA_LIST_PROJECTS- List all accessible projects to discover project keys.
Authentication
For setup instructions, see the Jira credentials page. Each step requires three configuration fields:| Config field | Description |
|---|---|
base_url | Your Jira site URL, e.g. https://your-domain.atlassian.net |
email | Your Atlassian account email |
api_token | A Jira API token (select from workspace secrets) |
Example: Create and Search Issues
Notes
- ADF conversion: Rich-text fields (description, comment body) accept plain text. The tool automatically converts each line into an Atlassian Document Format paragraph.
- Assignee: Jira identifies users by
accountId, not name or email. Pass theaccountIdvisible in the user’s profile URL. - At-least-once side effects:
JIRA_CREATE_ISSUEandJIRA_ADD_COMMENTmay create duplicates if a worker restarts after the call. De-duplicate downstream if exactly-once semantics matter. - Timeouts: Every request has a 30-second timeout via
AbortSignal.timeout.