Skip to content
Jira, Rovo

Email by default for summary automations

Summary agentic automations in Jira now start with email as the output, with Confluence still available as an alternative. It has been rolling out to Atlassian Cloud sites since 16 Nov 2026.

  • Rolling out since 16 Nov 2026
  • Medium impact

What it is

Improvement

When someone sets up a summary agentic automation in Jira, the output now starts as email instead of a Confluence page. The person creating it can still pick Confluence from the Output format dropdown. Choosing Confluence means picking a space and title, then deciding whether to send the report through Slack or Microsoft Teams.

Users

People creating a delivery health check or stakeholder status update automation see email preselected as the Output format. Daily standup automations keep their current behavior.

Written from Atlassian's release note and checked against it automatically. Atlassian's original stays the source of truth.

Where the rollout is

  1. First published Done
  2. Rollout starts Done

What changed

  1. Added to Atlassian's release notes as rolling out
  2. First published by Atlassian

Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.

Find out what an agent would inherit.

Fixed scope. The assessment reads the three layers an agent lands on, identity, platform and governance, before anything is switched on. You get the findings, the ownership gaps, and the order to close them in.