Teams | Collaboration | Customer Service | Project Management

@mention an agent on any page and it creates, edits, and comments alongside your team. Through the Atlassian Rovo MCP, the same agents work from Claude, Cursor, or your IDE. Agents have been working in Confluence since we launched custom agents in May 2024, and teams now run more than 5 million agent invocations a month. In February alone, Agents saved Atlassian customers more than 200,000 hours.

A reflection on building an enterprise product using AI agents, and what the data says about how we worked. The observation For the past few months we have been rapidly building an enterprise-wide, production-grade application that helps with employee compensation planning, management and communication. I compared what we built against a traditionally-built product to draw out insights about our new ways of working.

TLDR: Key updates: Rovo Search now provides AI-generated answers with citations, routes intent-aware queries in Jira, searches across 50+ connected tools, delivers richer visual results, and is embedded directly in Atlassian workflows. This blog summarizes improvements that have shipped over the past year to Rovo Search. Rovo Search keeps getting better over time! It is now approximately 60% faster than six months ago!

Your transformation strategy is only as strong as its alignment with team execution and financial investment. Now you can see portfolio health in real time, intervene before initiatives drift, and tie every request and dollar to the priorities that matter. The latest Strategy Collection innovations bring financial investment, delivery risk, and cross-team demand into one view. The best part? Every capability covered has shipped since our previous Innovation Spotlight.

Bring document knowledge you already have access to from Google Drive, SharePoint, and OneDrive into Rovo Search, Chat, and Agents so teams can move from questions to useful context faster. The project plan is in Google Drive. The financial model is in SharePoint. The work is tracked in Jira, and the decisions are documented in Confluence. Your team has the information it needs.

Connect any coding agent to your system of record to automate engineering loops AI coding agents have made individual developers faster. But faster individuals working in their local environments do not automatically create faster engineering organizations. The bottlenecks that slow software delivery are usually systemic: work stalls in human queues, triage waits for idle cycles, and routine handoffs depend on manual intervention.

AI is changing expectations for service. Employees want help that feels seamless. Customers want answers without long waits or repeated explanations. Operations teams want to get ahead of incidents and prevent disruptions rather than just respond. Those expectations rest on a critical dependency: context. AI is only useful when it can see the full picture – from people and knowledge to services, assets, and code – and all connections in between.

Each quarter, we ask some of our R&D teams to take a week away from the day-to-day to experiment and innovate on AI. We call this AI Builders Week, and it helps fuel our AI transformation. In past quarters, we’ve focused on building for individual workflows — how do we each get faster and more productive by inserting AI into different parts of our daily to-dos?

Great ideas can start with a random spark at 2 a.m., grow through a planning session with ChatGPT, or take shape in a brainstorm with Claude. AI helps you plan, but getting that plan into Trello has always been a manual, momentum-killing process. Today, that changes. Trello now uses MCP (a shared standard that lets AI tools talk to apps like Trello) to connect with assistants like Claude, ChatGPT, Gemini, and Cursor. That means you can manage your boards, lists, cards, and checklists just by asking.

For a long time, Jira was where you went to track work. You updated a status, closed a ticket. Something important has shifted now that agents can be assigned to work items. Jira is still a record of what happened, but now it’s something else too: a place where work can move between humans and agents. That shift got me thinking. What if I leaned into it fully and ran an experiment? What if each stage of the SDLC had its own specialized agent and the board itself handled the routing between them?