Atlassian’s October 30, 2026 autumn-release announcement introduces an agent usage dashboard in Jira’s space Reports tab. The company says the release is rolling out, with general availability across Jira Cloud by November. Before turning its charts into a team-performance statement, check which work the report actually covers.
Atlassian’s October 30 autumn-release announcement
A board filter does not define this report
Atlassian’s support documentation says space insights dashboards use the current Jira space, rather than an individual board or board filter. It also says agent reports depend on sessions linked to work items. Those are separate boundaries: the space establishes the reporting context, while session linkage affects which agent activity can appear.
Atlassian support: Agents dashboard scope and data requirements
Consider a fictional software space shared by a mobile team and a web team. The mobile team uses a board filtered to its own work. Opening a space-level report does not make that report a mobile-only report merely because the reviewer was previously looking at the mobile board. Labeling a screenshot “mobile team results” would need additional evidence about the population.
Write the population before reading the result
For a review, prepare a short note with the space name, the question being asked, the intended work-item population and the chosen dates. Keep the board’s filter description alongside it as a comparison, not as proof that the dashboard applied that filter. If the populations differ, revise the question or find a supported way to obtain the narrower evidence.
In the fictional example, suppose the question is whether agent-assisted mobile fixes moved through review sooner during a particular week. A chart for the shared space cannot answer that narrower question on its own. First identify the relevant mobile work items and the evidence needed to compare their review periods. Do not relabel a broader chart to make it fit.
An empty view needs a data check
The support page lists a paid Jira plan and enabled Rovo as prerequisites. For missing data, it advises checking activity in the selected space and dates; some delivery charts need completed items or sprints. It also describes a propagation delay of up to five minutes and supported agent experiences. Check current documentation for the experience you use.
Record what is missing precisely: an expected session, a work item, a completed period or the whole view. A blank chart alone is not enough to conclude that nobody used an agent. Likewise, a visible activity chart does not by itself establish that the agent caused a delivery improvement; the comparison needs matching populations and a clear definition of the outcome.
Keep the evidence with the screenshot
Save the observation time, selected space and dates, relevant work-item references and unresolved questions with any report you share. Ask a second reviewer whether the caption describes the population shown. This is a suggested review exercise, not a test of a live Jira tenant. No account access, session-linking behavior or delivery result was independently tested here.
Check the report’s scope
