Skip to content
Jira, Rovo

Choose who owns automated agent sessions

Automation rules that start Jira Coding Agent sessions now let you pick who owns each session. It has been rolling out to Atlassian Cloud sites since 15 Nov 2026.

  • Rolling out since 15 Nov 2026
  • Low impact
  • Admin review: prepare for this change

What it is

Improvement

In the Use Jira Coding Agent action, you choose one of three owners for the session: whoever owns the Rovo connection, whoever triggered the rule, or the assignee of the work item. Before, every session went to the Rovo connection owner. If the chosen owner can't be found when the rule runs, the rule fails.

Users

People who trigger a rule, or who are assigned the work item, can be set as the session owner and open that session themselves.

Admins

Rule authors set the session owner in the Use Jira Coding Agent action, and failed runs show error details in the rule's audit log.

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

Before it lands

  1. Review each rule that uses the Use Jira Coding Agent action and decide who should own its sessions.
  2. Check the rule's audit log for error details if a rule fails.

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.