JIRA_AUTH
An Atlassian API token expires, so check its date and reconnect.
Jira refused the connection.
JIRA_CONFLICT
The run waits and tries again.
Jira is already changing this object.
JIRA_FILE_INVALID
Check the file expression.
The file's contents are empty or not base64.
JIRA_FORBIDDEN
This account lacks a project permission, or issue security hides the issue.
Jira refused the request.
JIRA_INVALID_CONFIG
The node names which one.
A Jira setting on this node cannot be used as it stands.
JIRA_INVALID_REQUEST
The node names the fields it complained about.
Jira refused the request.
JIRA_INVALID_RESPONSE
Check the connection's site.
Jira answered something that is not JSON.
JIRA_NOT_FOUND
It also answers this when the account may not see it.
Jira has no issue, project or user by that id.
JIRA_REQUEST
Check the node's settings.
Jira refused the request.
JIRA_RESPONSE_TOO_LARGE
Ask for fewer fields, or a smaller page.
Jira answered more data than a run can parse.
JIRA_THROTTLED
The run waits and tries again.
Jira is rate-limiting this site.
JIRA_TOO_LARGE
The file is over this Jira site's attachment limit, which a Jira admin sets.
JIRA_TOO_MANY_RESULTS
Narrow the JQL, or read it page by page.
Jira returned more issues than a run can carry.
JIRA_TRANSITION_NOT_FOUND
The node lists the moves it can make.
Jira cannot make that move from where the issue is now.
JIRA_UNAVAILABLE
Try again once it is back.
Jira could not be reached.