Get Issue Changelog

jira.get_changelog
ActionBusiness appsconnection required

Calls the Jira Cloud REST API with the connection's email and API token.

Read the history of field changes on a Jira issue.

Connection

Required
Yes — the node will not save without one
Auth type
Username & password
Providers
Jira
Secret shape
{"email", "api_token"}
Config it needs
domain
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
issue_key
Issue key or numeric id, e.g. PROJ-123. Supports {{ }}.
stringYes———
start_at
Index of the first result to return, for paging through a long list.
numberNo0≥ 0—
max_results
Maximum results to return in one call.
numberNo100≥ 1—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_results": 100,
  "start_at": 0
}

Output

One shape.

result

FieldTypeExample
values[].id
The changelog entry's id.
string—
values[].created
When the change was made, ISO-8601.
string—
values[].author.displayName
Who made the change.
string—
values[].items
One entry per field changed, with from/to values.
array—
count
How many items this call returned.
number—
total
How many items match in total, when Jira reports one.
number—
start_at
Index of the first item in this page.
number—
is_last
True when this is the final page of results.
boolean—
{
  "count": 0,
  "is_last": false,
  "start_at": 0,
  "total": 0,
  "values": [
    {
      "author": {
        "displayName": ""
      },
      "created": "",
      "id": "",
      "items": []
    }
  ]
}

See Get Issue Changelog run in a workflow.

In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.