Jira Data Center icon

Jira Data Center

Interact with Jira Data Center API

Actions16

Issue → Get All

AI-generated

Overview

This node interacts with the Jira Data Center API to retrieve issues from a specified project. Specifically, the "Get All" operation under the "Issue" resource fetches multiple issues belonging to a given project. It supports returning either all issues or a limited number of them based on user preference.

Common scenarios where this node is beneficial include:

  • Automating reporting by fetching all issues for a project.
  • Integrating Jira issue data into other systems or dashboards.
  • Bulk processing or analysis of issues within a project.

For example, a user can configure this node to get all issues from the "PROJ" project and then use the output to generate a summary report or trigger further workflows based on issue statuses.

Properties

Name Meaning
Authentication Method used to authenticate with Jira Data Center API. Options: Personal Access Token, Basic Auth
Project The key of the Jira project to fetch issues from (e.g., PROJ).
Return All Whether to return all issues or limit the number of results.
Limit Maximum number of issues to return if "Return All" is false. Range: 1 to 500.

Output

The output is a JSON array where each element represents an individual Jira issue object as returned by the Jira Data Center API's search endpoint. Each issue object contains detailed information such as issue key, fields (summary, description, status, assignee, etc.), and metadata.

If "Return All" is enabled, all matching issues are returned; otherwise, only up to the specified limit are included.

No binary data is output by this operation.

Dependencies

  • Requires access to a Jira Data Center instance.
  • Requires authentication credentials configured in n8n, either via a personal access token or basic authentication.
  • The node uses Jira REST API endpoints under /rest/api/2/.

Troubleshooting

  • Authentication errors: Ensure that the provided API token or basic auth credentials are valid and have sufficient permissions to read issues in the specified project.
  • Project not found: Verify that the project key is correct and accessible by the authenticated user.
  • Limit exceeded: The maximum allowed limit is 500; setting a higher value will cause an error.
  • API request failures: Network issues or incorrect Jira server URL configuration can cause request failures. Check the server URL and network connectivity.
  • Empty results: If no issues are returned, confirm that the project contains issues and that the JQL query (project = <projectKey>) matches existing issues.

Links and References

Discussion