Coverage: 14 Sep to 21 Sep 2026
Welcome to TEEM360, your weekly pulse on the Atlassian ecosystem from ONETEEM.
This week is heavy on AI that teams can actually govern: Rovo Chat gets visible memory, shareable threads, @mentionable agents, and custom skills. Jira pushes governed agent loops for the AI-native SDLC. Admins get clearer sandbox, Connect end-of-support signals, and MCP v2. Forge and Bitbucket add practical developer guardrails.
Highlights
- 1. Rovo Chat (17 Sep): Visible memory controls, @mention agents in chat, shareable chats (permissions-aware), and custom skills built in natural language.
- 2. AI-native SDLC (10 Sep, still rolling): Code Context, agent loops (backlog to PR), Standards, AI Review, plus DX for Agentic Development and agent usage dashboards.
- 3. Admin and Cloud: Selective sandbox copy for Jira / JSM / Confluence, Connect end-of-support warnings in-product, Rovo MCP v2 across more apps, automation usage visibility.
- 4. Forge and Bitbucket: Forge asApp permission-check rollout, forge webtrigger create only, Bitbucket branch restrictions, Workflow Copy REST API.
- 5. Watch the calendar: State of AI SDLC digital summit on 22 Sep 2026.
At a glance
💬 Rovo Chat: context you can see, share, and reuse
Read More: https://www.atlassian.com/blog/company-news/rovo-chat-new-features-september-2026
Atlassian is pushing Rovo Chat from a personal assistant toward a team workspace:
• Memory you can edit: A memory view shows what Rovo learned (preferences, project facts). Users and admins can toggle memory on or off at user and site level.
• @mention agents: Bring a specialist agent into the same thread with full prior context.
• Share chats: Hand off the full thread (not a thin summary). Sharing stays permissions-aware.
• Custom skills: Describe a repeatable workflow in chat (or Rovo Studio); Rovo builds a reusable skill. Rolling out across instances over the coming week.
ONETEEM take: For customers already on Rovo, this is the week to define which skills belong in Chat vs Studio, and who may share chats outside the core team.
2. Governed agent loops for the AI-native SDLC
Atlassian's framing: 94% of engineering leaders use AI, but only 6% can scale it across the full software lifecycle. The response is a governed loop, not more one-off prompts.
• Code Context (Teamwork Graph): Secure intelligence across multi-repo codebases for planning, triage, and root cause. Open beta for paid customers.
• Agent Context Controls: Platform teams decide which agents operate in a space and what they can see.
• Agent loops in Jira: Scan well-defined unassigned work, send it to Jira Coding Agent, open review-ready PRs in Jira. Private early access.
• Standards + AI Review: Org coding standards mapped to repos; an agent reviews every PR against them before humans. Private early access.
• Measurement: DX for Agentic Development (throughput, quality, adoption, cost) and a Jira Agent Usage Dashboard.
Event: State of AI SDLC digital summit, 22 Sep 2026.
ONETEEM take: Treat agent loops like any other production automation: clear Definition of Ready for work items, Standards owned by platform, merge button still human.
3. Cloud and Admin: sandboxes, Connect sunset, MCP v2
Business-relevant items for admins this window:
• Selective sandbox copy: Copy specific Jira projects, JSM projects, or Confluence spaces into sandbox (with audit trail for JSM). Less “clone everything” friction.
• Connect end-of-support warnings: In-product banners in Jira, Confluence, and Administration for Connect apps. Start Forge migration planning if you have not.
• Rovo MCP v2: Single interface to more Atlassian apps (Jira, Confluence, Loom, Goals, Projects, Bitbucket, Focus, Teams, Talent, and more). Plan the upgrade from MCP v1.
• Automation usage dashboard: Clearer view of Automation steps and Rovo credit consumption ahead of billing model changes.
4. Forge, Bitbucket, and Jira APIs (developer desk)
• Forge asApp permission checks (17 Sep): Internal Jira permission evaluation change for asApp. No manifest change required; progressive tenant rollout.
• Forge CLI: Deprecated forge webtrigger root command removed. Use forge webtrigger create. Several list commands gain --json; errors go to stderr.
• Connect to Forge macros: migratedFrom on Forge macro modules maps old Connect macro keys so existing Confluence content keeps resolving.
• Bitbucket branch restrictions: Write / Merge access can now include repository, project, and workspace access tokens, Forge apps, and Rovo Dev.
• Workflow Copy REST API: POST /rest/api/3/workflows/copy creates a copy (with statuses) in the same scope as the source workflow.
• Jira Detail view deprecation (11 Sep): List / search detail toggle gives way to resizable preview panel or modal. App owners should verify UI modules.
Sources (primary)
1. https://www.atlassian.com/blog/company-news/rovo-chat-new-features-september-2026
2. https://www.atlassian.com/blog/jira/governed-agent-loops
3. https://confluence.atlassian.com/cloud/blog/2026/09/atlassian-cloud-changes-sep-7-to-sep-14-2026
4. https://developer.atlassian.com/changelog/
Closing
That is the mid-September pulse: Rovo Chat that remembers and shares, agent loops you can govern, and admin signals that Connect and release-note habits need a refresh before October.
Questions on Rovo rollout, Forge migration from Connect, or sandbox strategy? Reach out to ONETEEM. We help teams move from AI demos to governed delivery on Atlassian Cloud.
TEEM360 by ONETEEM
https://www.oneteem.com
