Skip to content

Jira Issue Handler

Jira Issue Handler connects your flow to your Jira Cloud to make changes: create issues and subtasks, change or delete them, and manage their comments, attachments, watchers and links to other issues.

It is useful when work starts outside Jira, for example in a support form, an email or a conversation with an AI agent, and you want it recorded as an issue without copying it by hand.

When to use it

  • Every bug a customer reports through the support form should create an issue of type Bug.
  • An AI agent helps the team and creates or updates issues when asked.
  • A customer replies by email and you want to add the reply as a comment on the issue.
  • You want to attach the files that come with a request to the issue.
  • One issue depends on another and you want to link them as “Blocks”.

Configuration

You need a Jira API credential with your Jira Cloud address, your Atlassian account email and an API token. See Credentials.

FieldWhat it does
Credential (required)The Jira API credential used to access your Jira.
Operation (required)What the component does. See Operations. Default: Create Issue.
ModeBasic shows only the essential fields; Advanced adds Description, Priority, Issue Status, Assignee Account ID, Comment and Custom Fields. Default: Basic. In the issue and subtask operations.
Project KeyThe Jira project. Once you pick the credential, the list shows your projects. Required to create. In the issue and subtask operations.
Issue SummaryThe issue’s title. Required in Create Issue and Create Subtask; in Update Issue and Update Subtask, only if you want to change it.
Issue TypeThe issue type (Task, Bug, Epic…). The list shows the chosen project’s types; when creating a subtask, only subtask types. In the issue and subtask operations.
Issue KeyThe issue key, for example PROJ-123. In every operation except Create Issue, Create Subtask, Delete Attachment and Delete Issue Link.
Issue Parent KeyThe key of the issue the subtask belongs to. In Create Subtask and Update Subtask.
Comment IDThe comment’s ID. In Update Comment and Delete Comment.
FilesThe files to attach, connected from another component. Only in Add Attachment.
Attachment IDThe ID of the attachment you want to delete. Only in Delete Attachment.
Watcher Account IDThe account ID of the person who starts or stops watching the issue. In Add Watcher and Remove Watcher.
Target Issue KeyThe key of the other issue in the link. Only in Create Issue Link.
Link TypeThe link type, for example Blocks or Duplicates. Only in Create Issue Link.
Issue Link IDThe ID of the link you want to delete. Only in Delete Issue Link.

Advanced mode fields

In Create Issue, Update Issue, Create Subtask and Update Subtask, with Mode set to Advanced:

FieldWhat it does
DescriptionThe issue’s detailed description.
PriorityThe priority (Low, Medium, High…). The list shows the project’s priorities. Not shown for subtasks or epics.
Issue StatusThe status the issue moves to (To Do, In Progress, Done…). Not shown for subtasks or epics.
Assignee Account IDThe account ID of the assignee. You get it with the List Users operation of Jira Reader.
CommentA comment added to the issue when you change it.
Custom FieldsValues for your Jira’s custom fields, for example {"customfield_10001": "value"}.

Operations

OperationWhat it does
Create IssueCreates an issue in a project.
Update IssueChanges an issue’s details. Only the fields you fill in are changed.
Create SubtaskCreates a subtask under an issue.
Update SubtaskChanges a subtask’s details.
Delete Issue / SubtaskDeletes an issue together with its subtasks.
Add CommentAdds a comment to an issue.
Update CommentChanges a comment’s text.
Delete CommentDeletes a comment.
Add AttachmentAttaches one or more files to an issue.
Delete AttachmentDeletes an attachment.
Add WatcherAdds a person to an issue’s watchers.
Remove WatcherRemoves a person from the watchers.
Create Issue LinkLinks two issues with the chosen link type.
Delete Issue LinkDeletes a link between issues.

Output

The Jira Response output returns the operation’s result: when creating or changing, the issue key, title, description, type, priority, status and assignee; in the other operations, a confirmation with the issue key and what was done. In Add Attachment you get one item per attached file.

You can connect the result to an email or messaging component to send a notice with the issue key, or to an agent so it can use it in its answer. The component can also be connected to an Agent as a tool. See Tool Mode.

Example

A support team wants every bug reported by a customer to create an issue in Jira.

  1. The support form reaches the flow with the problem’s title and description.
  2. Add Jira Issue Handler with the Create Issue operation and Mode set to Advanced.
  3. Choose the project in Project Key and Bug in Issue Type; put the title in Issue Summary and the description in Description.
  4. Connect Jira Response to an email component that sends the customer their issue key.

Good practices

  • Delete Issue / Subtask also deletes all subtasks and cannot be undone.
  • People’s account IDs are found with Jira Reader, List Users operation.