Actions16
Issue → Assign
AI-generatedOverview
This node integrates with Jira Data Center to manage issues programmatically. Specifically, the "Assign" operation for the "Issue" resource allows you to assign a Jira issue to a specific user by their username or account ID. This is useful in automated workflows where issues need to be dynamically assigned based on business logic, such as routing bugs to developers, assigning tasks to team members, or reassigning tickets after status changes.
Practical examples:
- Automatically assign newly created issues to a team lead.
- Reassign issues to a different user when transitioning the issue status.
- Batch assign multiple issues to a user based on priority or workload.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Personal Access Token" or "Basic Auth" |
| Issue Key | The unique key identifier of the Jira issue (e.g., PROJ-123) to assign |
| Assignee | Username or account ID of the user to whom the issue will be assigned |
Output
The output JSON contains an object indicating success of the assignment operation:
{
"success": true
}
This confirms that the issue was successfully assigned to the specified user.
No binary data is produced by this operation.
Dependencies
- Requires access to a Jira Data Center instance with API enabled.
- Needs either a Personal Access Token or Basic Authentication credentials configured in n8n.
- The node uses Jira's REST API endpoint
/rest/api/2/issue/{issueKey}/assigneewith HTTP PUT method.
Troubleshooting
Common Issues:
- Invalid or missing issue key: Ensure the issue key exists and is correctly formatted.
- Invalid assignee: The username or account ID must correspond to a valid user in Jira with permission to be assigned issues.
- Authentication errors: Verify that the API token or basic auth credentials are correct and have sufficient permissions.
- Network or server errors: Check connectivity to the Jira Data Center server and API availability.
Error Messages:
"Jira Data Center API request failed: ..."indicates an issue with the API call; check credentials, URL, and parameters.- Permission denied errors usually mean the authenticated user lacks rights to assign the issue.
Resolution Tips:
- Double-check input parameters for typos.
- Confirm user permissions in Jira.
- Test API credentials separately using tools like Postman.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.