/
Release Notes

Release Notes

v8.1.0 - June 2026

Improvements

  • Team-managed boards now appear in the console: Scrum boards from team-managed projects are listed alongside company-managed boards, so you can automate them too.

  • Cleaner handling of removed boards: automation switches itself off for a board that has been deleted or no longer supports sprints, instead of retrying it.

  • Reliability and quality improvements under the hood.

v8.0.0 - June 2026

New: manage every board in one place

  • Sprint Automation console: a new page under the Apps menu lists every Scrum board with its status, active sprint and last action. Turn automation on or off, configure it and review its history for any board from one screen.

  • Audit trail: each board keeps a record of every automated action, exportable to CSV or JSON.

More control over sprints

  • Auto-create up to five future sprints so your backlog always has somewhere to go.

  • Roll over unresolved work to the next sprint or back to the backlog, your choice per board.

  • Skip empty or dateless sprints so a placeholder never starts by accident.

Permissions

  • Only people with the Manage Sprints permission on a board's project can change its automation. Everyone else sees the settings as read-only. This matches the permission Jira already requires to start or close a sprint by hand.

Under the hood

  • The interface was rebuilt for a faster, more responsive experience.

  • The last action now shows how long ago it happened, and history is dimmed for boards where automation is off.

v7.0.0 - June 2026

  • Minor improvements

v5.5.0 - May 2026

  • Minor improvements

v5.4.0 - May 2026

UX

  • Inline help tooltips added next to Enable Sprint Autopilot and Unresolved work items.

  • Terminology: "tickets" is now "work items" everywhere, matching Atlassian Cloud terminology.

  • Date labels: Start date and End date now read Start date and time / End date and time.

  • Auto-create toggle: next sprint is auto-created whenever Unresolved work items is set to Move to next sprint and no future sprint exists.

v2.13.0 - April 2026

Performance

  • Unresolved issues fetched after sprint close, not before. Avoids expensive API calls when the close request itself fails.

  • Future sprint list cached within each close cycle and reused for both auto-create and issue routing.

v1.0.0 - April 2026

Initial release

  • Sprint Autopilot panel from the ... menu on every sprint card (Scrum boards only)

  • Full sprint editor: name, duration, start and end date and time, goal

  • Auto-start, auto-close, unresolved work item routing, auto-create next sprint

  • Per-board configuration with last action display