Jira Service Management, Confluence, Jira

Creating a Jira issue can now trigger an automation in Confluence

This Jira Service Management, Confluence and Jira change has been rolling out to Atlassian Cloud sites since 16 Dec 2024. Atlassian rates its impact low, and the tracker has not flagged it for admin review.

Rolling out since 16 Dec 2024
Low impact

Read Atlassian's release note See every change

Where the rollout is

First published 13 Dec 2024 Done
Rollout starts 16 Dec 2024 Done

What changed

13 Dec 2024 First published by Atlassian

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

Source Atlassian's release note Read it on the Atlassian Community

Related changes

Where it lands

Where this change sits on the Stack

Every change is sorted onto the layer it touches first. This one lands on Agents and Automation.

Agents and Automation

Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.

Atlassian Anthropic

Governance and Change

Permission architecture, audit and compliance, ITSM and change control, change management, strategic reporting and budgets.

Atlassian Guard Jira Service Management Strategy Collection Jira Align

Platform and Migration

Migration of every kind, tool consolidation, licensing, standardization, the system of work.

Atlassian Miro AWS Azure

Identity and Access

Human and non-human identity, SSO, SCIM, least privilege, access reviews, Guard cleanup, Agent SSO readiness.

Atlassian Guard Okta

load-bearing, bottom to top

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.

Book the assessment

By sending this you agree to our privacy policy.

Not ready? Talk to an architect