Sprint Automation for Jira: Release Notes (June 19, 2026)
Key Takeaways
The June 19, 2026 release of Sprint Automation for Jira Cloud focuses entirely on the Application logs experience and is available to every user with no configuration required.
Each log table now remembers its own sort column and direction, saved in your browser and restored automatically the next time you open the page.
Every log table (Configuration audit, Configuration history, and Automation logs) gained Export CSV and Export JSON buttons that export exactly the rows shown, so teams can analyze activity in a spreadsheet and keep records for compliance and audit.
Sprint lifecycle events (started, closed, created, updated, and deleted) are now recorded in the Automation logs table instead of only in internal server logs, giving audit-focused teams a visible history.
Release date: June 19, 2026
This release focuses entirely on the Application logs experience, making it easier to review, keep, and audit what Sprint Automation has done in your Jira site.
All changes are available to every Sprint Automation for Jira Cloud user. No configuration is required. The new options appear automatically on the Application logs page.
What's new
1. Your log sort order is now remembered
On the Application logs page, the column and direction you sort each log table by is now saved in your browser and restored automatically the next time you open the page. Each table remembers its own setting independently. Set it once and it stays the way you like it.
2. 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 in the table, so you can:
analyze sprint automation activity in a spreadsheet,
share log extracts with your team, and
keep records for compliance and audit purposes.
3. Fuller sprint-lifecycle audit trail
Sprint lifecycle events (started, closed, created, updated, and deleted) are now recorded in the Automation logs table on the logs page. Previously these were only written to internal server logs. This gives administrators, and especially enterprise customers with audit requirements, a clear, visible history of every sprint lifecycle change the app observed.