Jira

What it needs

A connection:

For each project: Issues assigned to you in this scope become Draft tickets (checked every minute), and moving a linked ticket to Done moves its issue.

Workflow triggers

Events that can start a workflow.

• Jira issue createdA new issue in a project's Jira scope (checked every minute; linking a project only records where it is).
• Jira issue updatedSomeone changed fields of an issue in a project's Jira scope (changed names them).
• Jira issue transitionedAn issue in a project's Jira scope moved to another status.
• Jira issue commentedSomeone commented on an issue in a project's Jira scope.

Workflow steps

• Test JiraSigns in with a Jira connection: {{steps.<id>.user}} is who it is; a connection that fails fails the step.
• Search JiraIssues a JQL query finds: {{steps.<id>.issues}} is a list of {key, summary, status, assignee, sprint, epic, placement, ticketId}; {{steps.<id>.next}} reads the next page.
• Read a Jira issueOne issue with its description and comments: {{steps.<id>.status}}, {{steps.<id>.sprint.name}}, {{steps.<id>.fields.<mapped name>}}.
• Import a Jira issueMakes a Draft ticket from a Jira issue (its summary and description), linked to it. When a ticket already links the issue nothing is made and the step leaves by exists: an issue is never imported twice.
• Create a Jira issueCreates an issue in a Jira project; its key is {{steps.<id>.key}}.
• Edit a Jira issueChanges an issue's fields or assignee; {{steps.<id>.changed}} lists the fields set.
• Comment on a Jira issueAdds a comment to a Jira issue; its id is {{steps.<id>.commentId}}.
• Jira issue's transitionsThe moves open to an issue now and the fields each needs: {{steps.<id>.transitions}}.
• Move a Jira issueMoves a Jira issue (by key, or a ticket's linked issue) through the transition named to, or the one leading to that status, with the fields its screen needs (fields). An issue already there counts as done; no such transition from its status leaves by unavailable; a required field left out fails the step, naming it.
• Jira boardsJira's boards: {{steps.<id>.boards}} is a list of {id, name, type, project}.
• Jira sprintsA board's sprints: {{steps.<id>.active}} is the active ones (backlog sections left out), {{steps.<id>.sections}} the backlog sections.
• Jira boardA board's issues with where each sits: {{steps.<id>.issues}}, each with placement {area: sprint, section, future or backlog; sprint; status}.
• Move Jira issues to a sprintMoves issues into a sprint (the board's active one, one by name or id, or a backlog section) or back to the backlog.
• Set Jira issues' epicPuts issues in an epic, or takes them out of theirs (epic empty).

Ready-made workflows

• Import assigned Jira issues (installed with it)
• Done moves the Jira issue (installed with it)

Tools

The PM can:

• jira_checkTest a Jira connection
• jira_searchSearch Jira with JQL
• jira_issueRead a Jira issue
• jira_importImport a Jira issue as a ticketasks you first
• jira_createCreate Jira issues and epicsasks you first
• jira_editEdit and assign Jira issuesasks you first
• jira_commentComment on Jira issuesasks you first
• jira_transitionsSee how a Jira issue can move
• jira_transitionMove Jira issues through their workflowasks you first
• jira_boardsList Jira boards
• jira_sprintsList a Jira board's sprints
• jira_boardSee where issues sit on a Jira board
• jira_sprintMove Jira issues between sprints and the backlogasks you first
• jira_epicPut Jira issues in an epic or take them outasks you first