
The Atlassian Rovo Governance Guide: Setting the Levers for Safe AI Adoption
Understand how Rovo governance works across permissions, admin controls, agents, automation, the MCP server, auditing, and Atlassian Guard.
Resources
Perspectives, release notes, and announcements from the team that builds apps and consults on Atlassian and ITSM.
Topics
More from the blog

Understand how Rovo governance works across permissions, admin controls, agents, automation, the MCP server, auditing, and Atlassian Guard.

Why did VIEW26 move from MongoDB to ClickHouse? As Jira Service Management datasets grew, Charts & Reports for JSM needed faster analytics at scale. ClickHouse now powers stronger dashboards, KPIs, filters, and reports for our Atlassian enterprises users

Test update from API

One JSM Incident queue. 200 tickets. Six legitimate chart types. Each chart, in isolation, points the team toward a different management action. The chart isn't a window onto the data — it is an editor. Here is the decision rule.

Every JSM ticket already carries a complete event log. Every queue holds 5–50 process variants nobody has drawn. Here's the read you can run on one queue in a week — without the seven-figure platform. We call it Ticket Replay.

A pragmatic guide to the ITSM dashboard metrics worth tracking — and the second reading behind each one that flips the diagnosis for JSM service desks.
Earlier
Thirty minutes with a senior specialist — no slides, no pitch.