Jira Data Center icon

Jira Data Center

Interact with Jira Data Center API

Actions16

Workflow → Get Transitions

AI-generated

Overview

This node integrates with Jira Data Center's API to interact specifically with workflows related to issues. The "Get Transitions" operation under the "Workflow" resource retrieves all available workflow transitions for a specified Jira issue. This is useful when you want to programmatically determine which status changes (transitions) can be applied to an issue before performing actions like moving the issue to a new state.

Common scenarios:

  • Automating issue status updates by first fetching possible transitions.
  • Building dynamic user interfaces that show only valid next steps for an issue.
  • Validating workflow states in bulk operations or integrations.

Example:
You have an issue with key PROJ-123 and want to know what statuses it can transition to next. Using this node, you provide the issue key, and it returns a list of transitions such as "Start Progress", "Resolve Issue", or "Close Issue".

Properties

Name Meaning
Authentication Method to authenticate with Jira Data Center API. Options: Personal Access Token, Basic Auth
Issue Key The unique key of the Jira issue to get transitions for (e.g., PROJ-123). Required.

Output

The output JSON contains an array of available transitions for the specified issue under the transitions field. Each transition typically includes details such as:

  • Transition ID: Identifier used to perform the transition.
  • Name: Human-readable name of the transition (e.g., "Start Progress").
  • To: The status the issue will move to after the transition.

If no transitions are available or the issue key is invalid, the output may be an empty array.

No binary data is produced by this node.

Dependencies

  • Requires access to a Jira Data Center instance.
  • Needs either a Personal Access Token or Basic Authentication credentials configured in n8n.
  • The Jira server URL must be provided in the credentials.
  • The node uses Jira REST API endpoints under /rest/api/2/issue/{issueKey}/transitions.

Troubleshooting

  • Invalid Issue Key: If the issue key does not exist or is malformed, the API call will fail. Ensure the issue key is correct and accessible by the authenticated user.
  • Authentication Errors: Incorrect or expired credentials will cause authentication failures. Verify that the API token or basic auth credentials are valid and have sufficient permissions.
  • Permission Denied: The authenticated user must have permission to view the issue and its workflow transitions.
  • API Request Failures: Network issues or incorrect Jira server URLs can cause request failures. Confirm the Jira server URL is reachable from n8n.
  • Empty Transitions List: Some issues might not have any available transitions if they are in a terminal state or the workflow restricts transitions.

Error messages returned by the node will generally include the Jira API error message prefixed with "Jira Data Center API request failed:".

Links and References

Discussion