Portal Community

Output Ports

PortDescription
successThe Jira API call completed successfully. Issue, project, or sprint data is available in output fields.
errorThe operation failed. Common causes: invalid API token, issue key not found, project key does not exist, invalid JQL syntax, invalid transition name, or insufficient Jira project permissions.

Issue Object Schema (issue/get & issue/create Output)

FieldTypeDescription
keystringThe Jira issue key in PROJECT-NUMBER format. Use this in subsequent issue/update, issue/addComment, or issue/transition calls.
idstringThe internal numeric Jira issue ID (as a string).
selfstringFull REST API URL for the issue resource.
summarystringThe issue title / summary line.
statusobjectCurrent workflow status. Contains name (e.g. "In Progress"), id, and statusCategory (To Do / In Progress / Done).
priorityobjectIssue priority. Contains name (e.g. "High") and iconUrl.
issuetypeobjectIssue type details. Contains name (e.g. "Bug"), id, and subtask boolean.
assigneeobjectAssigned user. Contains displayName, emailAddress, accountId, and avatarUrls. null if unassigned.
reporterobjectUser who created the issue. Same structure as assignee.
labelsarrayArray of label strings applied to the issue.
componentsarrayArray of component objects. Each contains id and name.
createdstringISO 8601 creation timestamp.
updatedstringISO 8601 timestamp of the most recent field update.
descriptionobjectIssue description in ADF format (or null if empty).
projectobjectParent project. Contains key, name, and id.
subtasksarrayArray of subtask summary objects (key, summary, status) if any subtasks exist.
comment.totalintegerNumber of comments on the issue.

Example: issue/create Output

{
  "key": "ENG-247",
  "id": "10247",
  "self": "https://yourorg.atlassian.net/rest/api/3/issue/10247",
  "summary": "[CRITICAL] Payment service connection timeout — production",
  "status": {
    "name": "To Do",
    "id": "10000",
    "statusCategory": { "name": "To Do", "colorName": "blue-gray" }
  },
  "priority":   { "name": "Highest", "iconUrl": "..." },
  "issuetype":  { "name": "Bug", "id": "10004", "subtask": false },
  "assignee": {
    "displayName": "Sarah Chen",
    "emailAddress": "sarah.chen@company.com",
    "accountId": "5b10ac8d82e05b22cc7d4ef5"
  },
  "reporter": {
    "displayName": "BizFirst Automation",
    "accountId": "5b10ac8d82e05b22cc7d4ef6"
  },
  "labels":     ["production", "critical", "payment-service"],
  "components": [{ "id": "10020", "name": "Payment Service" }],
  "created":    "2026-05-23T14:32:11.000+0000",
  "updated":    "2026-05-23T14:32:11.000+0000",
  "project":    { "key": "ENG", "name": "Engineering", "id": "10001" }
}

issue/getMany (JQL Search) Results Format

FieldTypeDescription
issuesarrayArray of issue objects matching the JQL query. Each element is a full issue object as described in the Issue Object Schema above.
totalintegerTotal number of issues matching the JQL query across the entire Jira instance (not just the returned page).
startAtintegerThe index of the first returned issue (0-based). Used for pagination.
maxResultsintegerThe maximum number of results returned in this response.

issue/transition Output

FieldTypeDescription
keystringThe issue key that was transitioned.
transitionNamestringThe name of the transition that was executed.
newStatusstringThe new status name of the issue after the transition.

issue/addComment Output

FieldTypeDescription
commentIdstringThe ID of the newly created comment.
createdstringISO 8601 timestamp of comment creation.
authorobjectThe user (or automation) who created the comment. Contains displayName and accountId.

sprint/get Output

FieldTypeDescription
idintegerSprint numeric ID.
namestringSprint name.
statestringCurrent state: active, closed, or future.
startDatestringISO 8601 sprint start date-time.
endDatestringISO 8601 sprint end date-time.
goalstringSprint goal text.
boardIdintegerThe board this sprint belongs to.
Reference the newly created issue key in downstream nodes with {{ nodes.createJiraIssue.output.key }}. Include it in Slack notifications, GitHub PR descriptions, or Notion database pages. Use {{ nodes.searchIssues.output.issues }} to iterate over JQL results in a Loop node.