Jira
Service domainPROJECT MANAGEMENT
Arcade Optimized
Arcade.dev LLM tools for interacting with Atlassian Jira
41tools
Jira Toolkit
The Jira toolkit by Arcade integrates with Atlassian Jira, enabling LLMs to create, read, update, search, and manage issues, sprints, boards, projects, and users through a comprehensive set of 41 tools.
Capabilities
- Issue lifecycle management — create, update, transition, comment on, label, and attach files to issues; read full issue details, comments, attachments, and available transitions
- Sprint & backlog operations — list and filter sprints by board or date range, add/remove issues to/from sprints, move issues to backlog, and retrieve sprint or backlog issue lists with pagination
- Board & project discovery — list and retrieve boards, projects, issue types, priority schemes, and their associations; batch-fetch multiple boards or sprints in a single call for performance
- Flexible issue search — structured parameterized search (preferred) for common filters (project, assignee, status, priority, labels, dates) and JQL-based search for advanced queries
- User & metadata lookup — resolve users by name, email, or ID; inspect priorities, labels, issue types, and Atlassian Cloud instances; establish caller identity via
WhoAmI
OAuth
This toolkit authenticates via OAuth 2.0 with Atlassian as the provider. See the Arcade Atlassian auth provider docs for setup details.
Available tools(41)
41 of 41 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
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. | |||
Add a comment to a Jira issue. | |||
Download the contents of an attachment associated with an issue. | |||
Get the metadata of an attachment. | |||
Get the details of a Jira issue by its ID. | |||
Get a comment by its ID. | |||
Get a transition available for an issue by the transition's ID or name.
When the transition is found by its name, the response contains the screen fields available
for the transition, if any. | |||
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 user information by their ID. | |||
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. | |||
Retrieve sprints from Jira boards with filtering options for planning and tracking purposes.
Use this when you need to view sprints from specific boards or find sprints within specific
date ranges. For temporal queries like "last month", "next week", or "this quarter",
prioritize date parameters over state filtering. Leave board_identifiers_list as None
to get sprints from all available boards.
DATE FILTERING PRIORITY: When users request sprints by time periods (e.g., "last month",
"next week"), use date parameters (start_date, end_date, specific_date) rather than
state filtering, as temporal criteria take precedence over sprint status.
Returns sprint data along with a backlog GUI URL link where you can see detailed sprint
information and manage sprint items.
MANDATORY ACTION: ALWAYS when you need to get sprints from 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.
BOARD LIMIT: Maximum of 25 boards can be processed in a single operation. If you need to
process more boards, split the request into multiple batches of 25 or fewer boards each.
Handles mixed board identifiers (names and IDs) with automatic fallback and deduplication.
All boards are processed concurrently for optimal performance. | |||
Get the metadata about the files attached to an issue.
This tool does NOT return the actual file contents. To read a file's content,
download the attachment by its ID. | |||
Get the comments of a Jira issue by its ID. | |||
Browse the priorities available to be used in the specified Jira issue. | |||
Get the issues for a given project. | |||
Get the transitions available for an existing Jira issue. | |||
Get the existing labels (tags) in the user's Jira instance. | |||
Browse the priority schemes available in Jira. |
Page 1 of 2(25 of 41)
Last updated on