Atlassian and OpenAI expanded their partnership on October 6, 2026, connecting OpenAI models with Atlassian’s workplace software and the organizational context held in its Teamwork Graph. The agreement broadens Atlassian’s access to models including GPT-6 Astra and the GPT-5.6 series, while extending the companies’ work on Rovo, ChatGPT and Codex. Their collaboration began in 2023. OpenAI’s announcement describes models powering agents across Rovo and the wider Atlassian platform.
For developers and engineering managers, the central distinction is between supplying reasoning capabilities and supplying the context needed to apply them. OpenAI provides the models; Atlassian’s Teamwork Graph connects people, projects, documents and decisions. Rovo combines those layers, while plugins bring Atlassian work information into ChatGPT and Codex.
How Rovo connects reasoning with company context
OpenAI says Rovo combines its reasoning capabilities with Atlassian’s Teamwork Graph. The Teamwork Graph supplies an enterprise context layer: relationships among the people doing work, the projects they contribute to, the documents describing that work and the decisions shaping it. Atlassian describes the combination as bringing organizational context to enterprise work in its partnership announcement.
That combination explains the division of labor. The graph contributes connected context about people, projects, documents and decisions; OpenAI models provide the reasoning capabilities. Rovo brings those layers together to ground reasoning in organizational context.
Expanded model access does not establish a Rovo default
The partnership gives Atlassian expanded access to GPT-6 Astra and the GPT-5.6 series. Those names identify models covered by the agreement; they do not establish which model handles every Rovo request.
VentureBeat reports that Atlassian explicitly said GPT-6 Astra is not becoming Rovo’s default model. According to that reporting, Rovo uses an internal AI gateway that routes dynamically across OpenAI and other providers, balancing capability, speed and cost for each task.
The same report says GPT-6 Astra shipped separately on September 3. The partnership announcement therefore concerns Atlassian’s access and integrations, rather than the model’s initial release. VentureBeat places the expansion within a partnership dating back to 2023.
For technical buyers, the implication is that the agreement strengthens one supplier relationship within an existing model mix. It does not justify assuming uniform GPT-6 Astra behavior across Rovo. The supplied evidence does not disclose the gateway’s routing rules, task-specific model assignments or comparative performance results, so it cannot establish how often a particular model will be selected.
Bringing Atlassian work into ChatGPT and Codex
The integration also runs in the other direction: Atlassian context can reach users working in OpenAI tools. The companies describe Atlassian plugins and MCP integrations powered by the Teamwork Graph that give ChatGPT and Codex users access to relevant work items, Confluence content and technical documentation.
Atlassian’s evidence says teams can connect ChatGPT and Codex through its plugin using open standards and the Model Context Protocol, or MCP. The documented purpose is to make relevant company information accessible within those tools. The supplied material does not include a configuration payload, installation command or permission mapping detailed enough to serve as an implementation guide.
OpenAI reports that more than 3,000 Atlassian developers use Codex across terminals, integrated development environments and code review workflows. Plugins powered by the Teamwork Graph give Codex users access to work items and technical documentation.
The adoption figure establishes reported internal use at Atlassian. It does not measure changes in code quality, development speed or review effort. For an engineering manager assessing these integrations, the concrete capability is access to project and technical context inside the development workflow; the productivity effect remains unquantified in the supplied evidence.
Model and context integrations across the companies
The announcements connect OpenAI models with Atlassian’s platform and bring Atlassian context into OpenAI tools.
| Integration or capability | Description in the evidence |
|---|---|
| OpenAI reasoning across Rovo and the Atlassian platform | OpenAI describes models powering AI experiences and agents. |
| Atlassian context in ChatGPT and Codex | Atlassian plugins and MCP integrations provide access to relevant work items, Confluence content and technical documentation. |
| Codex use within Atlassian engineering | More than 3,000 developers, according to OpenAI. |
OpenAI also says it will continue using Jira to manage critical workflows within its own company. That internal use is distinct from the model and context integrations described above.
Commercial terms and measurable outcomes remain open
VentureBeat reports that an OpenAI representative characterized the arrangement as effectively a spend commitment by Atlassian to OpenAI models and technology. The evidence supplies no commitment amount, term or customer pricing change.
The expanded partnership presents a concrete integration strategy: combine model reasoning with organizational relationships and expose that context in both Atlassian and OpenAI tools. What remains unresolved is how reliably those connections translate into better outcomes. Reported internal adoption and access to organizational context do not substitute for measurements of the quality, speed or cost of completed work.
