There is currently no public REST API to programmatically read Automation for Jira rule execution/audit log detail (at least I cannot find it) - the per-step trigger/condition/branch/action results and error messages that are only visible in the Automation admin UI. Use case: We run cross-schema JSM Assets + Jira Automation workflows (Hardware Assets / Users / Facilities) at production scale, with failure-notification emails routed to an on-call engineer. Triage today requires manually opening each audit log URL in the UI and copy-pasting the step-by-step trace to diagnose root cause (which component failed - trigger, condition, branch, or action - and the exact error text). This blocks: * Automated failure triage tooling (ingesting audit log detail into a ticketing/alerting pipeline instead of manual UI review per incident) * Building a queryable audit trail for compliance/change-management evidence * Correlating automation failures across multiple rules/schemas programmatically Request: Expose a REST endpoint (or extend the existing Automation REST API) that returns, per audit log ID: rule ID/name, execution timestamp, and the ordered list of trigger/condition/branch/action steps with their status and error text - equivalent to what the audit log UI already renders. Read-only access would fully unblock our use case. Related platform gap: We'd also flag this alongside the existing open request to raise the Lookup Objects action's 100-object cap - both point to the same underlying theme: Automation for Jira's admin/observability surface hasn't kept pace with its use as a primary automation engine for JSM Assets at scale. Happy to provide additional logs, rule IDs, or a call with our team if useful for prioritization. Thanks, José Nogueira

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Public REST API for Jira Automation Rule Audit Log / Execution Detail - Jira Cloud Automation

José Nogueira

There is currently no public REST API to programmatically read Automation for Jira rule execution/audit log detail (at least I cannot find it) - the per-step trigger/condition/branch/action results and error messages that are only visible in the Automation admin UI.

Use case:
We run cross-schema JSM Assets + Jira Automation workflows (Hardware Assets / Users / Facilities) at production scale, with failure-notification emails routed to an on-call engineer. Triage today requires manually opening each audit log URL in the UI and copy-pasting the step-by-step trace to diagnose root cause (which component failed - trigger, condition, branch, or action - and the exact error text).
This blocks:

Automated failure triage tooling (ingesting audit log detail into a ticketing/alerting pipeline instead of manual UI review per incident)
Building a queryable audit trail for compliance/change-management evidence
Correlating automation failures across multiple rules/schemas programmatically

Request:
Expose a REST endpoint (or extend the existing Automation REST API) that returns, per audit log ID: rule ID/name, execution timestamp, and the ordered list of trigger/condition/branch/action steps with their status and error text - equivalent to what the audit log UI already renders. Read-only access would fully unblock our use case.

Related platform gap:
We'd also flag this alongside the existing open request to raise the Lookup Objects action's 100-object cap - both point to the same underlying theme: Automation for Jira's admin/observability surface hasn't kept pace with its use as a primary automation engine for JSM Assets at scale. Happy to provide additional logs, rule IDs, or a call with our team if useful for prioritization.

Thanks,
José Nogueira

Accepted answers

Arkadiusz Wroblewski

Hello

That's already tracked here [AUTO-51] Official REST API to manage rules, export/import and access automation audit logs - Create and track feature requests for Atlassian products.

All comments

Arkadiusz Wroblewski

Hello

That's already tracked here [AUTO-51] Official REST API to manage rules, export/import and access automation audit logs - Create and track feature requests for Atlassian products.

Josh

The native gap is real: the audit-log UI detail is not the same thing as a supported public REST resource, so I would not build against undocumented endpoints. For a practical native workaround, add an error-handling path to each production rule (or standardize a reusable pattern) that creates/updates a dedicated incident issue and includes the rule name, execution time, issue/key context, and the relevant smart-value error text. A Send web request action can also push that small failure envelope to your logging/on-call system; avoid sending secrets or full Assets payloads.

Keep the Atlassian audit log as the authoritative per-step trace for deep diagnosis, and use the incident issue/external log for correlation and retention. If you need every branch/action result—not just failure context—then a public read-only endpoint is still the right feature request. Would a failure-only event stream meet the triage/compliance need, or do you specifically require complete successful execution traces too?

Josh

For a read-only workaround while AUTO-51 is open, I have seen teams emit their own minimal execution envelope from the rule: rule name/id, trigger issue key, {{now}}, a correlation id, and a short stage marker before each risky action. A Send web request action can post that JSON to an internal collector, and the failure branch can include the same correlation id plus {{ruleExecutionId}} if that smart value is available in your tenant. Keep the payload free of customer secrets and treat the Atlassian audit log as the source of truth; the external record is only an index/alert. This will not reproduce every UI step, but it makes cross-rule failure correlation and ticket creation possible until a supported audit-log endpoint exists.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation

log

jira-service-management