Jira Data Center icon

Jira Data Center

Interact with Jira Data Center API

Actions16

Issue → Get

AI-generated

Overview

This node integrates with the Jira Data Center API to perform various operations on Jira resources such as issues, projects, comments, users, and workflows. Specifically, for the Issue - Get operation, it retrieves detailed information about a single Jira issue identified by its unique issue key (e.g., "PROJ-123"). This is useful when you want to fetch the current state, fields, and metadata of a specific issue in your Jira instance.

Common scenarios include:

  • Fetching issue details to display or process in an automation workflow.
  • Retrieving issue data before updating or transitioning it.
  • Integrating Jira issue data into other systems or reports.

Example: You can use this node to get the full details of a bug report issue in Jira to analyze its status, assignee, priority, and description within an automated ticket management system.

Properties

Name Meaning
Authentication Method used to authenticate with Jira Data Center API. Options: Personal Access Token, Basic Auth
Issue Key The unique identifier of the Jira issue to retrieve (e.g., "PROJ-123"). Required field.

Output

The output JSON contains the full issue object as returned by the Jira Data Center REST API for the specified issue key. This includes all standard and custom fields of the issue, such as:

  • id: Internal ID of the issue.
  • key: The issue key (e.g., "PROJ-123").
  • fields: An object containing all issue fields like summary, description, status, assignee, reporter, priority, comments, etc.
  • Metadata about the issue type, project, creation date, update date, and more.

The structure matches the Jira API's issue representation, allowing downstream nodes or workflows to access any part of the issue data.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to a Jira Data Center instance with appropriate API access.
  • Supports two authentication methods:
    • Personal Access Token credential.
    • Basic Authentication credential.
  • The node expects the Jira server URL and credentials to be configured in n8n credentials for Jira Data Center API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing issue key: Ensure the issue key is correctly provided and exists in the Jira instance.
    • Authentication failures: Verify that the API token or basic auth credentials are valid and have sufficient permissions.
    • Network or connectivity errors: Confirm that the Jira server URL is reachable from the n8n environment.

  • Error Messages:

    • "Jira Data Center API request failed: <error message>" indicates an HTTP or API error. Check the error message for details such as 404 Not Found (issue does not exist) or 401 Unauthorized (authentication problem).
    • "The operation "get" is not supported for resource "issue" would indicate a misconfiguration but should not occur if using the node properly.

  • Resolution Tips:

    • Double-check the issue key format and existence.
    • Re-authenticate or update credentials if authorization errors occur.
    • Review Jira API permissions for the user associated with the credentials.

Links and References

Discussion