An agent running without context is just a token disposal service.
Today, we're announcing the new system for AI-native software development in Jira. 🧵
Jira is now the home base where developers and AI agents work side-by-side. 🤝
Assign a task, and Rovo Dev pulls context from your specs, writes the code, runs tests, and opens the PR—all on one board.
This is agentic SDLC, finally connected.
Atlassian is becoming the context layer for your business.
The formula: Information in. Intelligence out.
🤝 Connectors In: Pull signals from your entire toolchain.
🧠 The Graph: Data is mapped into the Teamwork Graph and compounds daily.
🔄 Context Out: Through our MCP
Sensitive data can pile up. Atlassian Guard Premium changes that.
New capabilities scan your entire Atlassian workspace to classify and protect data—whether it’s 15 years or 15 seconds old.
See what’s new: go.atlassian.com/comjet
The new Agent Sessions view in Jira gives you one place to manage agents running concurrently:
🔹 Spot and mitigate blockers instantly.
🔹 Approve or redirect agents without leaving the tab.
🔹 Delegate and decide like only a human can.
We’re working hard to make sure the @Atlassian Teamwork Graph is the best context graph for any organisation’s entire knowledge, work, people, code, physical assets and more. No matter where they’re stored, their permissions or their scale.
It is truly phenomenal and results in
Recently wrapped on a project creating a visual expression for the Teamwork Graph. As part of this work we launched an online experience where Atlassian users can log in and preview their own graph. Here’s a behind-the-scenes look at my favourite details from the project. 1/14
🛠 Jira tickets, Confluence docs, Rovo workflows, now available wherever your team is already talking. @Atlassian's Slack MCP integration lets you ask Slackbot questions in natural language to triage issues, check sprint status, retrieve project context, and create tickets
"We should create a ticket for that."
The most expensive sentence in engineering.
Not because work items are hard to manage, but because the "context tax" of moving a @SlackHQ conversation into Jira is a productivity killer. 🧵
Just mention @Jira in any @SlackHQ channel: @Jira create a bug for the login timeout discussed above.
It creates the structured work item without you ever leaving the conversation.