LoginSign Up
← Back to all sparks
A

Atlassian

PM
Velocity10.0

Maker of Jira, Confluence, Trello, Bitbucket, and the broader Atlassian collaboration suite.

www.atlassian.com ↗

Atlassian keeps feeding the Teamwork Graph — Salesforce is the newest source agents can read.

teamwork-graphagentic-workflowsintegrationsrovoai-governancecontext-engineering
◆Current state
The Inside Atlassian feed mixes research posts and AI thought leadership with a steady run of real releases, and the releases cluster on one idea: making the Teamwork Graph the context layer agents read from. Code Context brought multi-repo codebase understanding into it, a Salesforce connector now brings account, opportunity and case data, and agents already operate inside Confluence and through the Rovo MCP.
◆Where it's heading
Atlassian is competing on the index rather than the assistant. Each release widens what the Graph knows — repositories, CRM records, documents, service tickets — and the agent surfaces are deliberately open, running in Confluence, in Claude, in Cursor, in the IDE. Alongside that, the AI governance line signals a second front: selling oversight of the agents customers are already deploying.
◆Prediction
Expect more third-party systems connected into the Teamwork Graph on the Salesforce pattern, and governance packaged as a product rather than a posture.

◆Recent moves

  1. 2d ago

    Connect Salesforce to the Teamwork Graph to unlock customer context for your teams and agents

    A Salesforce connector pulls account, opportunity, contact and case records into the Teamwork Graph so Jira and Confluence work can be read alongside the customer context behind it. It extends the same context-layer strategy Code Context established, one source system at a time.

    View source ↗
  2. 2d ago

    Your next presentation is already in Confluence

    Confluence pages become the source for generated presentations, removing the manual rebuild from doc to deck. A useful surface on top of content Atlassian already holds, but incremental against the Graph work.

    View source ↗
  3. 5d ago

    Don’t Build AI Governance From Scratch. Just Turn It On.

    A positioning piece on turning on AI governance rather than building it. It frames a product direction without announcing one.

    View source ↗
  4. 7d ago

    Introducing the AI context engine for your entire codebase

    ⚡ SPARK

    Code Context put multi-repo codebase understanding into the Teamwork Graph, and the Salesforce connector that followed a week later shows it was a template rather than a one-off. This is the release that defined the current arc.

    View source ↗
  5. 7d ago

    3 AI bets powering Atlassian’s integrated marketing impact

    An internal marketing case study. No product content.

    View source ↗
  6. 8d ago

    You don’t need a team of AI experts. You just need one.

    Teamwork Lab research on the effect of a single AI superuser on team output. Research marketing supporting the AI narrative.

    View source ↗