What Shipped in September: The AI Meter Started Running

If you’ve switched on an AI agent or two this year and thought, “great, but who’s actually keeping an eye on these things?”, September was the month the vendors answered.

Last month the story was agents doing more real work. This month, all three of our core platforms shipped the other half: dashboards showing who’s using agents, tracking for the credits they consume, and tighter controls over what they can see and touch.

We track releases across Atlassian, Asana and ClickUp every month so our clients don’t have to comb through changelogs. Here’s what mattered in September, and where we’d spend your time.

The AI Bill Is Coming Into Focus

Atlassian redesigned the Usage tab in Automation to show which rules are consuming the most automation steps and Rovo credits, and it’s explicitly positioned as preparation for billing changes. That’s the line worth noting. A new Agents dashboard in Jira also shows how teams are actually using agents across Atlassian apps, and Rovo Dev is no longer available as a self-service signup, so new customers now go through sales.

Asana went the same way. Asana Dash and AI Teammates run on AI Requests, and admins now get a console view of total consumption, remaining balance, and proactive notifications as usage approaches monthly thresholds.

ClickUp’s angle is reuse rather than metering. You can now clone any Super Agent or save it as an organisation-wide template, so teams stop building the same agent five times over.

Why does this matter? Usage-based AI costs behave differently to seat licences. One poorly scoped rule firing on every work item can quietly burn through credits, and nobody notices until the bill arrives. The same discipline you’d apply to a licence review applies here, just with a monthly meter instead of an annual invoice.

And a fair counterpoint: not everything needs an agent. Asana also shipped round robin assignment in rules this month, and specifically calls out that it triages work without consuming AI credits. If a plain rule does the job, use the rule.

So What Can Your Agents Actually See?

The other half of governance is access. All three vendors tightened it up:

• Atlassian: a new Rovo MCP server control in Data Security Policy, with organisation-wide defaults and overrides by app, space and classification level. Gallery MCP servers can now use API token authentication with role-based access, and every Rovo agent session on a Jira work item is now visible to anyone with access to it.
• Asana: AI Teammates can connect to custom MCP servers using each user’s own authorisation, and a new read-only widget shows exactly which work items and attachments a teammate can access. Admins can also pre-authorise approved third-party apps through cross-app access, and require Microsoft SSO organisation-wide.
• ClickUp: private Custom Fields can now be shared with Super Agents at view, set or edit level, and you can share items to an agent straight from the normal sharing modal.

If your teams have connected external AI tools to Atlassian or Asana this year, it’s worth checking the new defaults line up with how you classify your data. These controls only help if someone actually sets them.

The Unglamorous Admin Stuff Worth Flagging

• Jira entity limits are now enforced. Jira now blocks actions that exceed limits on configuration entities like field options and workflows. Instances with years of accumulated custom fields and one-off workflows are the most exposed. The Site optimizer has new metrics for field options and security levels, so check before a project admin hits the wall mid-change.
• Two Jira reports are gone. The User workload and Version workload reports have been removed in favour of gadgets like the Workload pie chart. If anyone’s monthly reporting relied on them, they’ll notice.
• Company-managed software boards look different. They now match the modern business board look. Core functionality is the same, but a quick heads-up to your teams will save a few support tickets.
• Confluence Slack notifications have moved. The Slack tab is gone from space settings, and notifications are now managed from within the Slack app.
• Asana’s licensing model is shifting. Multi-product licensing gives Enterprise customers a more flexible way to manage access across Asana products. If a renewal is coming up, ask how it applies to you.

Quality of Life Wins Across the Board

• Jira and JSM: a new descendantsOfTeam JQL function, Rovo agents invoked with an @mention in JSM comments, a Resolve with Rovo summary for agents, native hardware asset management in JSM, and goal types with proper OKR support in Atlassian Goals.
• Confluence: a floating table of contents for long pages, permissions managed by teams, timeline view and checkbox fields in databases, and folder views that don’t need a blank parent page.
• Asana: threaded comments (finally), markdown that converts to rich text on paste, recoverable custom fields, @Asana in Slack for creating tasks from conversations, and a new automation builder that works across tasks, projects and portfolios in one rule.
• ClickUp: Meetings Hub pulls notes and recordings from SyncUps, Zoom, Google Meet and Teams into one searchable place, and a new “One assignee per group” toggle in List view means shared tasks show up in every owner’s lane.

Where We’d Focus If We Were You

Most of September needs nothing from you. But three things are worth a proper look: check your Atlassian Automation usage tab and Asana AI Requests console before billing changes land, review your MCP and agent access settings against your data classification, and run the Jira Site optimizer so entity limits don’t catch anyone out.

We help clients across Atlassian, Asana, ClickUp and Freshworks work out which releases are worth acting on and which are safe to let roll through quietly. If you want a second opinion on any of the above, or want the noise filtered for your instance specifically, get in touch with your account manager.