Release: Smarter Logs (Sort Memory, CSV/JSON Export & a Fuller Audit Trail)

Release: Smarter Logs (Sort Memory, CSV/JSON Export & a Fuller Audit Trail)

Key Takeaways

  • The Application logs page in Sprint Automation for Jira Cloud is now built for audit, export, and review, with the improvements appearing automatically and requiring no configuration.

  • Each log table remembers the column and sort direction you choose, saved in your browser and restored the next time you open the page.

  • Every log table (Configuration audit, Configuration history, and Automation logs) can be exported to CSV or JSON, with each export containing exactly the rows shown, for spreadsheet analysis, sharing, and compliance records.

  • Sprint lifecycle events (started, closed, created, updated, and deleted) are now recorded in the Automation logs table, whereas previously they lived only in internal server logs.

  • These log improvements give administrators and enterprise teams with audit requirements a clear, visible history of every sprint lifecycle change the app observed.

What's new: the Application logs page in Sprint Automation for Jira Cloud is now built for audit, export, and review: your sort order is remembered, every log table exports to CSV or JSON, and sprint-lifecycle events are recorded in the audit trail. No configuration required; the options appear automatically.

Your log sort order is now remembered

The column and direction you sort each log table by is saved in your browser and restored automatically next time you open the page. Each table remembers its own setting. Set it once and it stays the way you like it.

Export your logs to CSV or JSON

Every log table (Configuration audit, Configuration history, and Automation logs) now has Export CSV and Export JSON buttons. Each export contains exactly the rows shown, so you can analyze automation activity in a spreadsheet, share extracts with your team, and keep records for compliance and audit.

A fuller sprint-lifecycle audit trail

Sprint lifecycle events (started, closed, created, updated, and deleted) are now recorded in the Automation logs table. Previously these lived only in internal server logs. Administrators, and especially enterprise teams with audit requirements, now get a clear, visible history of every sprint lifecycle change the app observed.

How this compares to native Jira

Capability

Native Jira

Sprint Automation for Jira

Capability

Native Jira

Sprint Automation for Jira

Start & close sprints

Manual, one board at a time

Automatic, on schedule, across many boards

Roll over unfinished work

Manual during close

Automatic: next sprint, a new sprint, or backlog

Create the next sprint

Manual

Auto-created and auto-numbered

Audit trail of sprint automation

None for automated start / close / rollover

Every event recorded: started, closed, created, updated, deleted

Export activity

Not available

Export any log table to CSV or JSON

Remembered log preferences

None

Sort order saved per table

These improvements are available to all Sprint Automation for Jira Cloud users today.

Related resources