This document outlines the functionality and characteristics of the Jira Issue Writer node, which enables automated issue creation and updates in Jira projects.
These fields will appear in the node based on your Jira project’s configuration. Think of them as additional information you can add to your issue:
Description: The detailed write-up of your issue. While Summary is like a title, Description is where you can explain everything in detail.
Example: “When a user clicks the login button, nothing happens. This occurs on Chrome and Firefox browsers.”
Priority: How urgent the issue is. The options you see here come directly from your Jira settings.
Example: If your Jira has priorities set as “High”, “Medium”, “Low”, you’ll see these exact options in a dropdown.
Labels: Tags that help organize and find issues easily. You can add multiple labels to better categorize your issues.
Example: An issue might have labels like “frontend”, “bug”, “customer-reported”
Assignee: Who should work on this issue. The dropdown will show all users who can be assigned issues in your Jira project.
Example: If “Sarah Chen” and “Mike Smith” are members of your Jira project, you’ll see their names in the assignee dropdown.
Note: Use the ‘Configure Inputs’ option to expose these fields as inputs to the node. This is particularly useful for Loop Mode operations.
When you select custom fields in the Fields dropdown, they appear as input fields in your node. Here’s how to handle different types of custom field inputs:
Single-Value Custom Fields
Appears as: A text input field expecting a single value
Example: For a “Component” field, enter: “Frontend”
Note: Even though these might be dropdowns in Jira, they appear as text inputs in the node
Multi-Value Custom Fields
Appears as: A text input field that accepts multiple values
Example: For an “Affected Systems” field, enter: “Website,Mobile App,API”
Note: Use commas to separate multiple values
Cascading (Parent-Child) Custom Fields
Appears as: A text input field expecting a parent-child relationship
Example: For a “Location” field, enter: “North America > United States”
Note: Use the ”>” symbol to separate parent and child values
Generate an issue when a customer raises a ticket in your support system
Create a task when someone assigns you something in Slack
The node is perfect for any situation where you find yourself manually creating the same types of Jira issues repeatedly or need to create multiple issues at once.
Note: This node can only create new issues. It cannot update existing Jira issues.
Permissions: Node can only access projects and issues the authenticated user has permission to view
This node serves as a powerful tool for automating Jira issue management, enabling efficient project tracking, and streamlining workflow automation through flexible issue creation and update options.