Skip to content
TECH CEO Daily
SaaSDeal

Atlassian OpenAI partnership expands, connecting Jira and Confluence context to ChatGPT and Codex

OpenAI says its models will power agents across Atlassian's Rovo, while connectors let ChatGPT and Codex pull Jira and Confluence context under existing permissions.

By · Editor

· 2 min read · Fact-checked

The 60-second brief

  • 1Atlassian and OpenAI expanded their partnership on October 6, 2026, bringing OpenAI models into Rovo, Jira and Confluence.
  • 2Atlassian MCP Server connectors let ChatGPT and Codex draw on Jira and Confluence context, subject to permissions.
  • 3More than 3,000 Atlassian developers use Codex; pricing and per-product timelines were not disclosed.

The news

Atlassian (TEAM) and OpenAI expanded their partnership on October 6, 2026, linking Atlassian's project and knowledge tools more tightly to OpenAI's models and apps, according to reports by Crypto Briefing and FourWeekMBA on the companies' announcement.

The deal runs in two directions. OpenAI said its GPT-6 family of models will help power agents across Atlassian's platform, including Rovo, Atlassian's AI tool. Rovo pairs those models with the Teamwork Graph, Atlassian's map of how teams, projects, documents and decisions connect inside an organization.

In the other direction, Atlassian MCP Server connectors let data move between ChatGPT, Codex (OpenAI's coding agent) and Atlassian's tools. MCP, the Model Context Protocol, is an open standard for connecting AI apps to outside data. In practice, a developer working in Codex could pull project context from Jira without switching apps. FourWeekMBA reported that access stays subject to the organization's permissions and controls.

The two companies described the models' role slightly differently, FourWeekMBA noted: OpenAI said its models will power Atlassian's agents, while Atlassian described them as added to its mix of models. FourWeekMBA also reported planned features, including deeper integrations where agents pick up work items and run tests, and multi-agent orchestration with human checkpoints.

More than 3,000 Atlassian developers use Codex for software tasks, according to the reports. Pricing, contract terms and rollout timing for each product were not disclosed.

The numbers

Atlassian developers using Codex
3,000+
Announcement date
October 6, 2026

Why CEOs should care

For CIOs, the deal means Jira and Confluence content can flow into ChatGPT and Codex, tools many staff may already use. That is convenient, and it widens where sensitive project data can surface. Before turning on the connectors, confirm that Atlassian permissions carry through to ChatGPT results, check which ChatGPT plan your company holds and what it says about data use, and decide who can enable connectors.

For engineering leaders, the practical gain is less switching between a coding agent and the ticket that explains the work. Ask Atlassian which connector features are available now versus planned, and pilot with one team, measuring whether ticket context reduces rework before rolling out widely.

For CFOs and procurement, watch for double paying. Companies may end up paying for Rovo, ChatGPT seats and Codex usage that overlap. Ask both vendors how AI usage is billed through the integration before renewal.

The bigger picture

The deal shows a SaaS vendor choosing to plug into a major AI platform rather than try to keep users inside its own interface. Atlassian is betting that its value lies in the context it holds about how work gets done, which it can supply to whichever assistant employees prefer.

For OpenAI, connectors to systems such as Jira give ChatGPT and Codex the company knowledge they need to be useful at work, and strengthen its pitch to enterprise buyers.

What’s next

Watch for general availability dates for the Atlassian connectors in ChatGPT and Codex, any pricing changes for Rovo tied to OpenAI models, and whether rivals in work management announce similar ties with OpenAI or other model makers.

What “Fact-checked” means

Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.

What we checked
Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
How
A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
Who
The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, . A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
If something is wrong
“Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error

How we fact-check →

Companies in this story

Earlier coverage of Atlassian

All Atlassian coverage →

Written by

Editor · Technology & Business Writer

Hussein is a writer and business technology enthusiast focused on the intersection of technology, entrepreneurship, finance, artificial intelligence, and digital innovation.

CoversAICybersecurityBig TechSaaSStartupsFintech

About this story. Researched from primary sources whenever they are available and fact-checked before publication.

Published by Tech CEO Daily, an independent publication. Masthead · Editorial standards

Follow Tech CEO Daily on Facebook for the day’s top stories in your feed.

Free newsletters

The technology briefing for people running businesses.

Daily, weekly, bi-weekly or monthly. You choose.

How often

The Daily Brief · Monday to Saturday, 7 a.m. ET

Free forever. One click to unsubscribe. We never sell your email.