Mattering Automations Jira integration

Get an approximate count of the issues matching a JQL query without fetching them. Much cheaper than a search when you only need the number.

Find users who can actually be assigned to an issue or in a project. Safer than a plain user search, because not every user is assignable everywhere.

Get the metadata for one attachment: filename, size, MIME type, author, and the URL its content lives at. The file itself is not returned.

Check whether attachments are enabled on the site and what the maximum upload size is, in bytes.

Get one board by id, with its type and the project or user it lives in.

Get a board's columns, the statuses mapped to each, its filter, and its estimation field. This is how you learn what Done means on that board.

Get a single comment on an issue by its id, including author, body, and visibility restrictions.

Get one component by id, including its project, lead, and assignee rule.

Get the Atlassian account the API token belongs to: account id, display name, email, and time zone. Use this to confirm the credential works.

List the fields on an issue that the credential can actually edit, with their allowed values. Read this before building an Update Issue body against an unfamiliar project.

Get one epic by id or key. Gotcha: this endpoint does not work for epics in team managed projects, use Get Issue there instead.

Get one saved filter by id, including its JQL, owner, and share permissions.

Get one issue by id or key, for example EX-1. Set fields to a short list to keep the response small, because the default returns every field including custom fields.

Get the field change history of an issue, oldest first, with the author and the before and after values of each change.

Get one issue link by id, including both linked issues and the direction of the relationship.

Fetch up to 100 issues by id or key in one request. Issues that could not be read come back in issueErrors rather than failing the call.

Get every field name, operator, and function that JQL accepts on this site, plus the reserved words. This is the vocabulary an agent needs to write valid JQL for a specific site.

Get one project by id or key, including its lead, type, and URL. Project keys are case sensitive.

Get information about the Jira site itself: base URL, version, build number, server time, and time zone.

Get one sprint by id, with its state, goal, and start and end dates.

Get one user by Atlassian account id. Email may be hidden depending on that user's privacy settings.

Get one version by id, including whether it is released, archived, or overdue.

List every user on the site, active and inactive, page by page. Capped at 1000 per page and needs the Browse Users and Groups permission.

List the workflow transitions the issue can take right now, with their ids and target statuses. Transition ids are workflow specific, so read them here before moving an issue.

List the backlog of a board, meaning incomplete issues not in any active or future sprint. Paging uses nextPageToken.

List the epics on a board, with their colour and done state.

List the issues on a board, including Jira Software fields such as sprint and epic. Paging uses nextPageToken, not startAt.

List the projects a board draws issues from. A board can span several projects when its filter allows it.

List the sprints on a board. Filter by state to get just the active one, which is the usual starting point for a standup automation.

List the Jira Software boards the credential can view, optionally filtered by type or project. Requires a Jira Software licence on the site.

List the issue types the credential can create in a project, with their ids. Issue type ids differ per project, so read them here rather than assuming them.

List the issues under an epic, ordered by rank. For team managed projects, search with JQL on parent instead.

List every system and custom field on the site with its id, name, and JQL clause names. This is how you map a custom field name to its customfield_ id.

List the fields available when creating one issue type in one project, including which are required and what values they accept. This is how you discover custom field ids.

List the groups a user belongs to, by Atlassian account id. Useful for permission checks before an automation acts on someone's behalf.

List the comments on an issue. Comment bodies come back as Atlassian Document Format, so expand renderedBody if you want HTML instead.

List the link types configured on the site, such as Blocks or Duplicate, with their inward and outward wording. Needed before creating a link.

List all issue types visible to the credential, across every project it can browse.

List the issue types in one project. Takes the numeric project id, not the project key.

List who is watching an issue and how many watchers it has.

List the time logged against an issue, oldest first. Time tracking has to be enabled on the site or this returns an error.

List every label in use on the site, page by page. Labels are free text in Jira, so this is the only way to see what already exists.

List the filters owned by the credential's user, and optionally their favourites too.

List the issue priorities on the site, optionally narrowed to the ones available in given projects.

List every component in a project, with its lead and default assignee rule. Not paginated.

List the project roles and the URL for each role's members. Roles are shared across all projects on a Jira Cloud site.

List the valid statuses in a project, grouped by issue type. Statuses differ per issue type, which is why they are nested.

List every version, meaning release, in a project with its release date and released flag. Not paginated.

List up to 20 projects the credential's user viewed most recently. Handy as a cheap orientation call.

List the links from an issue to things outside Jira, such as a support ticket or a document.

List the resolutions on the site, such as Done or Won't Do. Needed when a transition screen requires a resolution.

List the issues in a sprint, ordered by rank, including Jira Software fields such as story points and flagged. Paging uses nextPageToken.

List every status used by an active workflow on the site, with its status category.

Find saved filters by name, owner, or project. Expand jql if you want the query text, it is not included by default.

Search issues with a JQL query. Two gotchas: the query must be bounded, so include a filter such as project or updated, and paging uses nextPageToken from the previous response rather than an offset.

Same search as the JQL search node, but the query travels in a JSON body. Use this when the JQL or the field list is too long to fit in a URL.

List the projects the credential can see, with paging and filters. Use this rather than assuming project keys.

Find active users by name or email fragment. Needs the Browse Users and Groups permission, and returns account ids you can use to assign issues.

Parse and validate JQL queries before running them, returning the parsed structure or the errors. Useful when an agent composes JQL and you want to fail early instead of on the search.

Add a comment to an issue. Gotcha: v3 requires Atlassian Document Format, a plain string body is rejected.

Add a user as a watcher on an issue. Gotcha: the body is a bare JSON string holding the account id, not an object.

Link an issue to an external URL. Gotcha: this is an upsert, a call carrying an existing globalId overwrites that link and blanks any field you leave out.

Set the assignee on an issue by Atlassian account id. Works even for users who only hold the Assign Issues permission, not full edit rights.

Create a component in a project. Components group issues inside a project and can set a default assignee.

Save a JQL query as a reusable filter. It is created with the site's default share scope and is not favourited.

Create an issue or subtask. Gotcha: description and other rich text fields must be Atlassian Document Format, and the response returns only the new id, key, and self URL, not the whole issue.

Create up to 50 issues in one call. Partial success is normal: check the errors array in the response, because valid issues are still created when others fail.

Create a project from a project template. Needs Jira administrator rights, and the template key has to match the project type key.

Create a future sprint on a scrum board. It is created in the future state, use Update Sprint to start it.

Create a version, meaning a release, in a project. Note that projectId is numeric, so look it up with Get Project if you only have the key.

Permanently delete an attachment from an issue. Deleting another user's attachment needs the Delete All Attachments permission.

Permanently delete a comment from an issue. Deleting another user's comment needs the Delete All Comments permission.

Delete a component. Set moveIssuesTo to hand its issues to another component, otherwise they are simply left without one.

Permanently delete an issue. An issue that has subtasks cannot be deleted unless deleteSubtasks is true, which deletes those too.

Remove the link between two issues. The issues themselves are untouched.

Delete a project and everything in it. Needs Jira administrator rights, and an archived project has to be restored before it can be deleted.

Permanently delete a worklog entry. Use adjustEstimate and increaseBy if the remaining estimate should be given the time back.

Create a link between two issues, for example blocks or duplicates. Gotcha: the response body is empty, so read the issue back if you need the new link id.

Log time against an issue. By default Jira reduces the remaining estimate automatically, use adjustEstimate to change that.

Move up to 50 issues back to the backlog, which removes them from any future or active sprint.

Move up to 50 issues under an epic. An issue can only sit in one epic, so this removes it from any previous one.

Move up to 50 issues into a sprint. Only future and active sprints accept issues, a closed sprint is rejected.

Reorder issues by ranking them before or after another issue. Gotcha: a partial failure returns HTTP 207 with a per issue status list rather than a plain error.

Stop a user watching an issue. Removing anyone other than yourself needs the Manage Watchers permission.

Queue a Jira email notification about an issue to its reporter, assignee, watchers, or named users. The mail is sent by Jira, so it comes from the site's own notification address.

Move an issue to a new status by transition id. Get the id from List Available Transitions first, because the same status has different ids in different workflows.

Replace the text of an existing comment. The whole body is overwritten, so send the full new text rather than a fragment.

Update a component's name, description, lead, or assignee rule. Fields you send are overwritten outright.

Edit fields on an issue. Gotcha: this cannot change status, use Transition Issue for that, and the response is empty unless you set returnIssue.

Update project details such as name, description, lead, or URL. Changing the key or a scheme needs Jira administrator rights.

Partially update a sprint, including starting or completing it through the state field. On a closed sprint only the name and goal can still change.

Update a version, for example to mark it released or move its release date. This is how an automation closes out a release.

Change an existing worklog entry, such as its duration, start time, or comment.