INTEGRATION

Jira actions

Create and manage issues, comments, attachments, worklogs, and users in Jira

Actions
25
Maintained by
Flomation

Every Jira action

  • Add AttachmentAttach a file to a Jira issue. Provide the issue key, a file name (e.g. report.pdf) and the file's bytes as base64: Flomation uploads it to the issue. Returns the created attachment's details.
  • Add CommentAdd a comment to a Jira issue. Enter the issue key (e.g. SCRUM-1) and the comment text: it is posted as a plain-text comment on the issue.
  • Add WorklogLog time spent on a Jira issue. Give the issue key and how long was spent (e.g. "1h 30m"), optionally add a comment and set when the work started. Returns the new worklog entry.
  • Create IssueCreate a Jira issue. Pick the project and issue type, set a summary and description, and optionally assign it, set a priority, add labels or link a parent (for subtasks). Any other field can be set via Custom Fields or Additional Fields.
  • Create UserInvite a new user to your Atlassian site by email address. Optionally set a display name and choose which products to grant access to (leave products empty to invite the user to every product). Requires organisation-admin permission on the site.
  • Delete AttachmentPermanently delete a Jira attachment by its ID. This removes the file from its issue and cannot be undone.
  • Delete CommentPermanently delete a comment from a Jira issue. Enter the issue key (e.g. SCRUM-1) and the comment ID to remove. This cannot be undone.
  • Delete IssuePermanently delete a Jira issue by its key. Optionally delete the issue's subtasks along with it. This cannot be undone.
  • Delete UserRemove a user from your Atlassian site by their account ID. This deletes the user from the site: requires organisation-admin permission.
  • Delete WorklogRemove a worklog entry from a Jira issue by its issue key and worklog ID. This permanently deletes the logged time and cannot be undone.
  • Get AttachmentFetch a Jira attachment's details by its ID. Optionally download the file itself: when Download File is on, the file's bytes are returned base64-encoded on the File Content output.
  • Get CommentFetch a single comment from a Jira issue by its ID. Enter the issue key (e.g. SCRUM-1) and the comment ID to return the full comment.
  • Get IssueFetch a single Jira issue by its key. Optionally narrow the returned data to specific fields, or expand extra sections such as the changelog or rendered fields.
  • Get Issue ChangelogRetrieve the full change history of a Jira issue: every field edit, status move and assignment, in order. Return all history entries, or cap them to a limit.
  • Get Many AttachmentsList every attachment on a Jira issue. Provide the issue key; the attachments are read from the issue itself. Turn on Return All to get them all, or set a Limit to cap how many are returned.
  • Get Many CommentsList the comments on a Jira issue. Enter the issue key (e.g. SCRUM-1) and either return everything or cap the number returned. Optionally order by newest or oldest first.
  • Get Many WorklogsList the worklog entries logged against a Jira issue. Return every entry, or cap the count with a limit. Each entry includes who logged it, the time spent and any comment.
  • Get UserLook up a single Atlassian user by their account ID and return their profile. Optionally expand extra details (e.g. groups, applicationRoles) via the Expand field.
  • Get WorklogFetch a single worklog entry from a Jira issue by its issue key and worklog ID. Returns the full worklog, including who logged it, the time spent and any comment.
  • List TransitionsList the status transitions currently available for a Jira issue: the moves it can make from its current status. Use a transition's ID with Update Issue to change the status.
  • Notify About IssueSend an email notification about a Jira issue. Set a subject and message body, and choose who receives it: the reporter, assignee, watchers, voters, or named users and groups.
  • Search IssuesSearch Jira issues using a JQL query. Leave the query blank to list every issue, or narrow the search and choose which fields to return. Return everything, or cap the results to a limit.
  • Update CommentChange the text of an existing comment on a Jira issue. Enter the issue key (e.g. SCRUM-1), the comment ID, and the new comment text.
  • Update IssueUpdate an existing Jira issue. Change any of the standard fields, and optionally move the issue to a new status by choosing a transition. Leave a field blank to leave it unchanged.
  • Update WorklogChange an existing worklog entry on a Jira issue. Update the time spent, the comment or when the work started: supply only the fields you want to change. Returns the updated worklog.

Wire Jira into the rest of your stack

Every action here drops onto the canvas alongside the other 3,585, so a Jira step can sit between a form, a database and a message without any glue code.