Agentic Index
Atlassian change log
Agentic Index tracks material product changes at Atlassian and has logged 4 entries since September 10, 2026. Each entry is dated, sourced from the vendor's own materials or the press, and carries a change type and an impact level, so it can be read against Atlassian's capability coverage across the 14 point Agentic Index taxonomy.
Read the Atlassian assessment →
Follow this change log by RSS
Free for your reader, newsletter or automation tool. One feed covers the whole index, and every category has its own.
Public-source research. All entries are sourced from official vendor blogs, changelogs, documentation, or press materials. Support levels marked Needs Review or Publicly Claimed should be independently verified before relying on them for procurement decisions.
4 entries matching filters
MCP / tool calling / API
Six tools on Atlassian MCP V2 now return rich UI cards in MCP clients instead of plain text: getJiraIssue, editJiraIssue, createJiraIssue, transitionJiraIssue and searchJiraIssuesUsingJql in Jira, and searchConfluence in Confluence. The rollout reaches customers in steps, and Atlassian asks anyone who does not see the cards by October 23 to contact support.
Teams working on Jira and Confluence from Claude, ChatGPT or other MCP clients can check an agent's issue edits and transitions in a rendered card rather than raw tool output, which makes reviewing agent actions quicker.
MCP / tool calling / API
Forge developers can now build a Rovo action once and expose it as a tool both to custom agents in Rovo Studio and to outside MCP clients such as Claude Desktop, Codex and Cursor, with the rovo:mcp module now in Preview. Outside access is off by default and switched on per app installation, and every tool call runs under the user's existing site permissions.
Teams building on Forge can reach outside AI clients from one tool definition instead of separate integrations, while admins keep an opt in switch per installation.
MCP / tool calling / API
Atlassian began rolling out five capacity planning tools in Rovo MCP, grouped under read_capacity_planning and write_capacity_planning. Agents can retrieve allocations, search nonproject work, update allocations, and create or update nonproject work. Organization administrators control access to the toolsets in Atlassian Administration.
Teams can connect planning assistants to staffing allocations with separate read and write permissions. Buyers should confirm tenant rollout and explicitly enable the appropriate toolsets before relying on automated planning workflows.
Agent capability
Atlassian introduced the Early Access Program for Skills for Rovo Agents, allowing developers to package reusable, task-specific instructions and reference files within Forge apps. This new module enables tool orchestration by coordinating multiple actions into a complete workflow and integrates with custom agents in Rovo Studio.
Developers and administrators can now build more complex, multi-step workflows for their Rovo agents, extending the agent's ability to handle specialized tasks autonomously.
Current rankings
These changes feed the index. See where each category stands: the best vendors of 2026, ranked by verified capability coverage.
Capability coverage
Every change above is graded against the same 14 capability axes. Each axis has its own page showing how much of the index documents it, which categories concentrate it, and the leading platform in each.
The AI agent directory for business · The full feature taxonomy · Pricing research
What has changed at Atlassian recently?
The most recent change Agentic Index logged at Atlassian is dated October 13, 2026. Six tools on Atlassian MCP V2 now return rich UI cards in MCP clients instead of plain text: getJiraIssue, editJiraIssue, createJiraIssue, transitionJiraIssue and searchJiraIssuesUsingJql in Jira, and searchConfluence in Confluence. It is one of 4 dated, sourced entries the index holds for Atlassian.
Common questions
How do I keep up with changes to AI agent platforms?
Read one maintained change log instead of tracking each vendor's release notes separately. The Agentic Index change log records 1895 verified updates across agentic AI platforms, updated weekly, covering new agent capabilities, MCP and tool calling changes, memory, human approval controls, observability, deployment options, pricing and funding. Every entry names the vendor, the date, the change type and an impact level, and links to that vendor's profile.
How often is the agentic AI change log updated?
Weekly. The most recent update was Oct 31, 2026, covering Smithery, Anthropic Claude Code, Capy.
How do I track changes for one specific AI agent vendor?
Filter the change log by vendor, or open that vendor's profile page, where the same verified entries appear alongside its capability coverage across the 14 point Agentic Index taxonomy.
Where can I find a single feed of agentic AI platform updates?
This page is that feed. Agentic Index reviews vendor blogs, changelogs, documentation and press materials every week and files what materially changed, so keeping up with changes to AI agent platforms is one page rather than several hundred. Entries are filterable by vendor, change type, impact level and verification status, and each one carries the evidence basis it was graded from. The same entries are published as a free RSS feed at agenticindex.io/feeds/changes.xml, with one feed per ranking category listed at agenticindex.io/use-this-data.
Last updated: Oct 31, 2026 · 1895 tracked changes across 580 vendors