Atlassian vs Jira

Two things are happening on Atlassian's feed at once. Rovo is being pushed past Atlassian's own data — Search, Chat, and Agents now draw on Google Drive, SharePoint, and OneDrive documents the user already has access to — while the developer platform finishes a forced migration, with Connect end of support arriving and over 95% of paid app seats already moved to Forge. Alongside those, the Strategy Collection ties financial investment and delivery risk to portfolio work, and Trello picked up seven AI features across all paid tiers. The remainder of the feed is Inside Atlassian engineering essays and Teamwork Lab research rather than shipped product.

Rovo's value is being framed as coverage rather than cleverness: the pitch is that it answers from wherever the document actually lives, which makes each additional file store worth more than another model upgrade. Underneath, Forge is becoming the only place third-party code runs, and with the Forge LLMs API now GA those apps inherit model access from the platform instead of bringing their own. The two threads meet at context — Atlassian is positioning itself as the layer that knows where the work, the money, and the documents are, then renting that context to its own agents and to partner apps on the same terms.

Expect the connected-context list to keep growing toward the remaining major document stores rather than stopping at Microsoft and Google, and expect post-Connect Forge messaging to shift from migration deadlines to what apps can do with platform-supplied models.