Jira
Service domainPROJECT MANAGEMENT
Arcade Optimized
Arcade.dev LLM tools for interacting with Atlassian Jira
43tools
Jira Toolkit
Arcade toolkit for Atlassian Jira that lets LLMs create, read, update, and manage Jira issues, sprints, boards, users, and attachments via the Atlassian REST API.
Capabilities
- Issue lifecycle: Create, update, transition, comment on, label, and search issues — via parameterized search or raw JQL. Preferred tool is parameterized search; JQL is available as fallback or when the user supplies a query directly.
- Attachments: Attach files (raw string or base64), list attachment metadata, and download attachment contents.
- Sprint & backlog management: List and filter sprints across boards (up to 25 boards per call, date-range and state filtering), add/move issues to sprints, move issues back to backlog.
- Boards, projects & priorities: Retrieve boards, projects, issue types, priority schemes, and priority availability scoped to a project or issue — with automatic ID resolution so callers can pass names, keys, or emails instead of raw IDs.
- Users: Look up users by ID, display name, or email; list all users; retrieve the currently authenticated user's profile and available Atlassian clouds (
WhoAmI— call first to establish context). - Metadata & discovery: List labels, available transitions for an issue, comment retrieval by ID, and Atlassian cloud enumeration.
OAuth
Authentication uses OAuth 2.0 via the Atlassian provider. See the Arcade provider docs for setup details: https://docs.arcade.dev/en/references/auth-providers/atlassian
Available tools(43)
43 of 43 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a comment to a Jira issue. | |||
Add a list of issues to a sprint.
Maximum of 50 issues per operation. | |||
Add labels to an existing Jira issue. | |||
Add an attachment to an issue.
Must provide exactly one of file_content_str or file_content_base64. | |||
Create a new Jira issue.
Provide a value to one of `project` or `parent_issue` arguments. If `project` and
`parent_issue` are not provided, the tool will select the single project available.
If the user has multiple, an error will be returned with the available projects to choose from.
If you have an issue type name, or a project key/name, a priority name, an assignee
name/key/email, or a reporter name/key/email, DO NOT CALL OTHER TOOLS only to list available
projects, priorities, issue types, or users. Provide the name, key, or email and the tool
will figure out the ID. | |||
Download the contents of an attachment associated with an issue. | |||
Get the metadata of an attachment. | |||
Get available Atlassian Clouds. | |||
Get all issues in a board's backlog with pagination support.
Returns issues that are not currently assigned to any active sprint.
The backlog contains issues that are ready to be planned into future sprints.
Only boards that support backlogs (like Scrum and Kanban boards) will return results. | |||
Retrieve Jira boards either by specifying their names or IDs, or get all
available boards.
All requests support offset and limit with a maximum of 50 boards returned per call.
MANDATORY ACTION: ALWAYS when you need to get multiple boards, you must
include all the board identifiers in a single call rather than making
multiple separate tool calls, as this provides much better performance, not doing that will
bring huge performance penalties.
The tool automatically handles mixed identifier types (names and IDs), deduplicates results, and
falls back from ID lookup to name lookup when needed. | |||
Get a comment by its ID. | |||
Get the details of a Jira issue by its ID. | |||
Get the comments of a Jira issue by its ID. | |||
Search for Jira issues when you don't have the issue ID(s).
All text-based arguments (keywords, assignee, project, labels) are case-insensitive.
ALWAYS PREFER THIS TOOL OVER THE `Jira.SearchIssuesWithJql` TOOL, UNLESS IT'S ABSOLUTELY
NECESSARY TO USE A JQL QUERY TO FILTER IN A WAY THAT IS NOT SUPPORTED BY THIS TOOL. | |||
Get the details of a Jira issue type by its ID. | |||
Get the details of a priority by its ID. | |||
Get the details of a Jira project by its ID or key. | |||
Get all issues that are currently assigned to a specific sprint with pagination support.
Returns issues that are planned for or being worked on in the sprint. | |||
Get a transition by its ID. | |||
Get a transition available for an issue by the transition name.
The response will contain screen fields available for the transition, if any. | |||
Get the transitions available for an existing Jira issue. | |||
Get user information by their ID. | |||
Get users without their account ID, searching by display name and email address.
The Jira user search API will return up to 1,000 (one thousand) users for any given name/email
query. If you need to get more users, please use the `Jira.ListAllUsers` tool. | |||
Get the metadata about the files attached to an issue.
This tool does NOT return the actual file contents. To get a file content,
use the `Jira.DownloadAttachment` tool. | |||
Get the issues for a given project. |
Page 1 of 2(25 of 43)
Last updated on