rocketkind
Project management

Jira

Jira Cloud tracks issues, projects and the work moving through them.

Authentication

  • OAuth 2.0 (3LO)

Actions

Generic API request. Call any Jira API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Add commentPost a comment on a Jira issue, for example to record a decision or notify watchers from an automation.
  • Add worklogLog time spent against a Jira issue so it counts towards the issue's time tracking and any report built on it.
  • Assign issueDestructiveSet or clear the assignee of a Jira issue by Atlassian account id, for routing work from an automation.
  • Count issuesEstimate how many issues match a JQL query without reading them, for example to report how many of a project's issues are in each status category or are overdue.
  • Create issueRaise a new issue in a Jira project.
  • Create issue linkRecord a relationship between two existing Jira issues, such as one blocking or duplicating the other, using the link type name and the two issue keys.
  • Create projectCreate a Jira project with its key, name, type and lead.
  • Delete issueDestructivePermanently delete a Jira issue by id or key.
  • Get current userRetrieve the currently authenticated Jira user (GET /myself).
  • Get issueRead one Jira issue by id or key with every field, for example to report its status, assignee, links and description in depth.
  • Get projectRetrieve a single Jira project by id or key (GET /project/{projectIdOrKey}).
  • Get transitionsList the workflow transitions available for a Jira issue (GET /issue/{issueIdOrKey}/transitions).
  • List assignable usersList the users who can be assigned to a given Jira issue (or to issues in a given project) — the lookup behind jira:assignissue, since that call takes an Atlassian accountId rather than a name.
  • List boardsList the Jira Software boards the connected user can view, filtered by project, name or type — the first step to a board's sprints, since jira:listsprints takes a numeric boardId.
  • List commentsRead the comment thread on a Jira issue, for example to summarise the discussion or to check whether a bot already replied.
  • List issue typesList all issue types visible to the user (GET /issuetype).
  • List projectsList projects visible to the user, paginated (GET /project/search).
  • List sprint issuesList the issues in one sprint, ranked as on the board, optionally narrowed by a JQL clause — the read for a sprint review or standup once jira:listsprints has given the sprint id.
  • List sprintsList a scrum board's sprints, optionally only the active, future or closed ones — how to find the current sprint's id and dates before reading its issues with jira:listsprintissues.
  • List usersList every user of the Jira site the credential can browse, to resolve a person to the Atlassian accountId that project and issue calls take.
  • Search issuesFind issues across projects with a JQL query: the general purpose read action when you do not already hold an issue key.
  • Search usersFind users by name, email, or display name (GET /user/search?query=...).
  • Transition issueDestructiveMove a Jira issue through a workflow transition (POST /issue/{issueIdOrKey}/transitions, 204 No Content).
  • Update issueDestructiveChange fields on an existing Jira issue by sending only what you want to set: summary and description as plain text (the Atlassian Document Format document is assembled for you), anything else in the fields map.

Triggers

  • Comment added (webhook)Starts the instant a new comment is added to a Jira issue, delivered by a webhook instead of waiting for the next poll.
  • Issue commentsAnswers as an agent on Jira issues: when someone mentions the connection's user in a comment — or, if you choose, assigns them an issue or creates any issue — the agent replies in the issue's comments, and later comments on that issue continue the conversation.
  • Issue created (webhook)Starts the instant a new Jira issue is created, delivered by a webhook instead of waiting for the next poll.
  • New commentStarts when a new comment is posted on the selected Jira issue, found by polling that issue's comments ordered newest-created first.
  • New or updated issueStarts when a Jira issue is created or updated in the connected site, across every project the connection can see.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.