Connect Jira to your ERP

Search for issues using JQL (Jira Query Language).

Searches for issues using JQL with enhanced search capabilities.

Returns all sprints from a board, for the given board ID.

Returns all issues in a sprint.

Retrieves available options for the Labels field.

Lists all comments for an issue.

Returns all epics from a board, for the given board ID.

Returns all issues that belong to an epic on the given board.

Returns all boards.

Returns all issues from a board, for the given board ID.

Gets the details for a list of users.

Gets details of user.

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status.

Gets the status of a long-running asynchronous task.

Returns the sprint for a given sprint ID.

Gets the details for an issue.

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user.

Returns lists of issues matching a query string.

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with Search Issues with JQL (e.g. assignee = '{accountId}') or Assign Issue. Requires a Cloud ID to identify the Jira site.

Lists all accessible Jira Cloud sites and their IDs.

Returns the board for the given board ID.

Gets metadata on all projects.

Provide an estimated count of the issues that match the JQL.

Checks whether one or more issues would be returned by one or more JQL queries.

Updates an issue. A transition may be applied and issue properties updated as part of the edit.

Updates a comment.

Performs an issue transition and, if the transition has a screen, updates the fields from the transition screen.

Moves issues to a sprint, for a given sprint ID.

Downloads a Jira issue attachment's binary content to the configured file-stash directory and returns its saved path plus the attachment's metadata (filename, mimeType, size, etc.). Use this after locating an attachment via Get Issue (its fields.attachment[] array lists each attachment's id, filename, size, and mimeType), or from an attachment reference surfaced by another Jira action or trigger — pass that id as attachmentId. The file is saved in the file-stash directory as <attachmentId>-<sanitized filename> (the ID prefix avoids collisions when multiple attachments share the same filename); the returned filedata tuple points at that saved path for use in downstream file-input props. Jira's content endpoint responds with a redirect to a signed, short-lived media URL — this is followed automatically, so no extra configuration is required.

Deletes a project.

Creates a project version.

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask.

Creates a future sprint.

Create a context for custom field options.

Assigns an issue to a user.

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added.

Adds multiple attachments to an issue.

Adds a new comment to an issue.

Adds an attachment to an issue.