Use Jira as a trigger to kick off a workflow, or use it as an action to do something automatically in your workflow.
Triggers when Jira webhook events are received. Real-time notifications for Jira events like issue created, updated, deleted, etc.
Adds one or more attachments to an issue. Requires Browse Projects and Create attachments permissions.
Adds a comment to an issue. This operation can be accessed anonymously.
Assigns an issue to a user. Can assign to specific user, default assignee, or unassign.
Bulk fetch changelogs for multiple issues and filter by fields. Returns a paginated list of all changelogs for given issues sorted by changelog date and issue IDs.
Returns the details for a set of requested issues. You can request up to 100 issues.
Returns a paginated list of the users specified by one or more account IDs. (Experimental)
Creates an issue or subtask. Permissions required: Browse projects and Create issues project permissions.
Creates a user. This resource is retained for legacy compatibility. As soon as a more suitable alternative is available this resource will be deprecated.
Deletes an attachment from an issue. Requires "Delete own attachments" or "Delete all attachments" project permission.
Deletes a comment from an issue. This action cannot be undone.
Deletes an issue. Can optionally delete subtasks if they exist.
Deletes a user. If the operation completes successfully then the user is removed from Jira's user base. This operation does not delete the user's Atlassian account.
Edits an issue. Fields can be updated using either direct field setting or update operations.
Returns the account IDs for the users specified in the key or username parameters. (Experimental)
Returns a list of all users, including active users, inactive users and previously deleted users that have an Atlassian account. Permissions required: Browse users and groups global permission.
Returns the contents of an attachment. Supports range requests for partial downloads. Requires Browse Projects permission.
Returns the attachment settings for the Jira instance, including whether attachments are enabled and the maximum attachment size allowed. No permissions required.
Returns the thumbnail of an attachment. Supports custom dimensions and fallback options. Requires Browse Projects permission.
Returns a paginated list of all changelogs for an issue sorted by date, starting from the oldest.
Returns changelogs for an issue specified by a list of changelog IDs.
Returns a specific comment from an issue. This operation can be accessed anonymously.
Returns all comments for an issue. This operation can be accessed anonymously.
Returns a paginated list of comments specified by a list of comment IDs. This operation can be accessed anonymously.
Returns the details for an issue by its ID or key. Supports comprehensive field and expand options.
Returns all issues breaching and approaching per-issue limits. Requires Browse projects and Administer Jira permissions.
Returns either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. Requires Browse Projects permission.
Performs an issue transition and, if the transition has a screen, updates the fields from the transition screen. Requires Browse Projects and Transition Issues permissions.
Updates a comment. This operation can be accessed anonymously.
Retrieve a Jira user by account ID, username, or email
Returns the default issue table columns for the user. If accountId is not passed, the calling user's details are returned.
Search for Jira users by query string
Creates an email notification for an issue and adds it to the mail queue. If no recipients are specified, defaults to assignee and reporter. Requires Browse Projects permission.
Returns the groups to which a user belongs. Permissions required: Browse users and groups global permission.
