Audit log

Every action recorded: what happened, who triggered it, who it was attributed to, and whether it succeeded.

The audit log is Proxy Agent's accountability layer. Every comment, transition, edit, link change, and worklog action is written to a record stored inside your Forge tenant.

Where to find it

ScopeWhere
Site-wide Jira → System settings → Apps → Act as Agent Configuration → Audit log tab. Visible to Jira admins.
Per project Project settings → Act as Agent → Audit log tab. Visible to project admins. Filtered to this project.
audit-log-overview
Audit log table with a few rows visible, filter bar above

Columns

ColumnWhat it shows
TimeWhen the action ran, in your locale's date-time format.
ActorThe user who clicked the button. Their avatar and display name.
ActionWhat they did: Add comment, Transition issue, Edit issue, Add link, Remove link, Log work, Upload attachment.
IssueThe issue key and (on hover) summary the action affected.
Acted asApp if the action ran in app mode, or Impersonation with the configured agent's name.
StatusSuccess (green) or Failed (red).
DetailsA View / Hide toggle for the per-action payload (transition ID, field values changed, link IDs, error message, etc.).

Filtering

The filter bar supports:

  • Date range: From/To pickers. Defaults to the last 30 days.
  • Action: narrow to one action type, or "All actions."
  • Actor: search any Jira user; show only actions they triggered.

Click Apply to commit the filters. Reset clears them. Refresh re-runs the current filter set.

audit-log-filtered
Audit log filtered to "Transition issue" actions by a specific actor in the last 7 days

Pagination

Results are paginated. Click Load more at the bottom to fetch the next page. Default page size: 50.

Details panel

Click View in the Details column to expand the payload for that record. Examples:

  • For a comment: whether the comment had a body, how many attachments, the ADF body.
  • For a transition: the transition ID, any fields set during the transition, whether the optional comment was successfully added.
  • For a link change: the link type, direction, and both endpoints.
  • For a failure: the captured errorMessage from Jira's API.
audit-log-details-panel
Audit entry expanded showing JSON payload of a transition with fields and comment status

What's stored

Each record includes: timestamp, issueId, projectId (frozen at action time; does not follow the issue if it moves), userAccountId of the actor, action, actAsMode, actAsAccountId (in impersonation mode), success, an optional errorMessage, and an action-specific details blob clamped at 200 KiB.

Retention

Records are retained for 90 days and then auto-expire. There is no manual purge.