If anyone in your organisation receives a dashboard by email on a schedule from Atlassian Analytics, Assets Reports or Jira Service Management Operations Reports, that email has a retirement date. Atlassian published the notice on 10 August on the Analytics articles board, where most JSM and Assets admins never look, so here is the admin translation, with the part the notice does not say: what a scheduled replacement looks like. 📅
The Jira Cloud changelog entry describes 2 November as full removal "for low-touch customers," which reads as if other customers may see a different timeline. Nothing I can find spells that out, so treat 2 November as your date unless Atlassian tells you otherwise.
Why 8 September is the one to plan around: after that day you cannot create a subscription, which means you cannot set up a temporary one while you test the replacement, and you cannot fix a broken one by recreating it. Whatever you have on 8 September is what you run out with.
Stops: scheduled subscription emails (PDF or zipped CSVs) from Analytics dashboards, Assets Reports and JSM Operations Reports.
Stays: chart and dashboard export as CSV, PDF or JSON, on demand; sharing links; embedding a live dashboard as a Smart Link in Confluence or Jira; data shares.
Atlassian's suggested replacement is manual: export a PDF when needed and share it by email or chat, bookmark the dashboards you use, ask the creator for exports. That works for a team of five. It does not work for the weekly management pack that 40 people expect on Monday morning, which is what most of these subscriptions are.
There is no workspace-wide list of subscriptions in the documentation, so the inventory is per dashboard: open each dashboard, then Settings, then the Subscriptions tab, per Atlassian's setup page. For each one record the recipients, the frequency, and whether it sends PDF or CSV, because the replacement depends on that last column. For Assets Reports and JSM Operations Reports the subscribe control sits on the report itself; check each report you know is emailed. Ask your dashboard owners to do the same; the people who created subscriptions are the only ones who see them.
1. "People need the numbers on a schedule" (CSV subscriptions, list-shaped data). If the underlying data is Jira work items, a saved filter with a filter subscription does this natively and did before Analytics existed: run the filter, Details, New subscription, choose a frequency, choose yourself or a group. Groups require the Manage Group Filter Subscriptions global permission, and every recipient gets only the work items they can browse (Manage filters). It is a list, not a chart, but for "which requests breached SLA this week" it is the same information.
2. "Leadership wants the visual on a schedule" (PDF subscriptions). Two honest options. Embed the live dashboard as a Smart Link on a Confluence page and send the page link on a schedule with a Jira or Confluence automation rule; leadership gets a live, always-current view instead of a stale PDF. Or, if you are on Enterprise with a BI tool in the building, use a data share to feed the Atlassian Data Lake into that tool and let its scheduler send the PDF (What is a data share). The second is more work and more durable.
3. "Someone needs a heads-up when a threshold is crossed." This was never a good fit for a dashboard email. Build it as an automation rule with a scheduled trigger and a JQL condition that sends only when the count is non-zero. Fewer emails, more signal.
All links verified live on 2 September 2026.
Sami Shaik
0 comments