Looking back: Atlassian Finance User Forum – Spring 2026

1. What's New in the Atlassian World – Lukas Herzog (Atlassian)

Atlassian's strategy is clearly focused on AI – not as an add-on, but as a fundamental component of the platform. The central principle: Acceleration = Intelligence × Context.

Rovo and the Teamwork Graph

Rovo is Atlassian's AI platform, defined as: AI Gateway × Teamwork Graph. The Teamwork Graph connects data from Jira, Confluence, Loom, Google Drive, Slack, Microsoft Teams and more into a unified organisational context.

The model works across three dimensions:

• Extend context – integrate data from all tools (Data Catalog, Business Glossary, quality monitoring)
• Leverage context – embed AI agents directly into workflows
• Externalise context – make Atlassian knowledge available outside the platform (e.g. via MCP)

Key Announcements

• Agents in Jira – embedded in workflows, accessible via chat and automation, and assignable as owners
• Teamwork Graph in MCP (Open Beta) – Figma, Claude, VS Code and Cursor can access Atlassian context
• Teamwork Graph CLI (Open Beta) – delivers 44% better output quality and 48% fewer token consumption compared to conventional methods

"Bad data isn't a new problem, but AI is exposing it more." — Group Vice President of Product Development, Fortune 500 Technology Company (State of Teams 2026)

Key Takeaway: Context! Context! Context! An AI model alone is not enough – real value comes from the quality and depth of context an organisation has built. Atlassian has positioned itself natively on this with the Teamwork Graph, and you can feel it.

2. Trusted Cloud: Atlassian for Regulated Institutions – Tom Hausman (Atlassian)

One of the most pressing questions for Swiss financial institutions is: can you migrate to Atlassian Cloud and still remain FINMA-compliant? The clear answer: yes.

Swiss banks are already running Atlassian Cloud today – FINMA-compliant, with enterprise-grade controls – alongside institutions regulated by EU-DORA and UK-FCA/PRA.

The Regulatory Landscape in Switzerland

The central FINMA question is: "If a critical service goes down – how quickly do you recover, and is your data intact?" – That is exactly what Atlassian Cloud was built for.

Die vier Säulen der Compliance

Pillar 1 – Trusted by Design

• Audit certifications: SOC 2 Type 2, ISO 27001/27018, ISO 22301, BSI C5 Type 2
• Architecture: globally distributed Multi-AZ, cell-based isolation, DR testing, Zero Trust, layered encryption
• Incident transparency: real-time status, post-incident reports, DPA notification commitments
• Shared responsibility: Atlassian secures the platform – you are responsible for your usage and retain audit control

Pillar 2 – Data Residency Zurich (AWS eu-central-2)

• Stored in Zurich: issues, pages, comments, attachments (Jira, JSM, Confluence)
• Global services: identity, notifications, AI inference, search indexing
• Encryption: TLS 1.2+, AES-256, customer managed keys via AWS KMS

Pillar 3 – Navigating Cloud & Regulation

• FINMA RS 2018/3 + 2023/01 are principles-based and technology-neutral – enabling adaptation for cloud
• Manage Marketplace apps independently through your own vendor risk process
• Three-tier audit strategy: third-party reports (SOC 2, ISO, C5) → due diligence under DPA → extended audit rights via FSA

Pillar 4 – Migration & Exit Hygiene

• Migration in: end-to-end encrypted, Zero Trust Access, residency target from day 1
• Exit out: native export, Backup & Restore APIs, EU Data Act portability, FSA transition assistance

Key Takeaway: "Planning a clean way in means planning a clean way out."

Atlassian Cloud is FINMA-ready. Anyone who addresses the three key areas – Risk Governance, Marketplace Management and Audit Strategy – can migrate to the cloud in full regulatory compliance.

3. Can Your Organisation Afford a Data Governance Failure? – Michał Cheba (GitProtect)

http://GitProtect.io , part of the Xopero Group, is a leading backup provider for DevOps and Jira environments with over 16 years of experience, 100,000+ customers and a presence in 60+ countries.

Why Backup is Not Optional

Data loss can result from cyberattacks, accidental deletion, AI errors, natural disasters, outages and compliance failures.

Examples from the talk:

• Jaguar Land Rover: a cyberattack caused USD 890 million in damages, triggered a global IT shutdown and production stoppages.
• Vocalink (Mastercard subsidiary): the Bank of England imposed a £11.9 million fine for governance failures – the first such case for financial market infrastructure.

The Shared Responsibility Model

GitHub, GitLab, Microsoft and Atlassian all recommend third-party backups. Providers secure hosting and applications – you are responsible for users, policies, apps and data protection.

What Matters When Choosing a Backup System

• Ease of use
• Flexible deployment (cloud, on-premise)
• Comprehensive data coverage
• Control over your own storage
• Configurable schedule and retention
• Strong encryption
• Notifications
• Fast, simple recovery

Key Takeaway: Compliance frameworks such as ISO 27001, SOC 2, NIS 2 and DORA make backup a requirement – not an option. Backup and compliance are inseparable today.

4. Cloud Migration Is Not Just a Game – Anja Fuchs (Swarmit)

Key lessons from numerous Atlassian Data Center-to-cloud migrations, seen through the lens of board games.

MONOPOLY – Ownership & Cleanup

Every space and every project gets kept. Clean up? Later.

Typical issues: many Jira projects with outdated workflows, orphaned Confluence spaces, complex schemes, unclear project ownership.

"Those who hoard and never let go block the whole game."

Key Takeaway: Clean up first, then migrate.

CHESS – Governance & Strategy

Migration is won before the first move. Set the course early: data security and compliance (GDPR, data residency, industry-specific), licence optimisation (the right model saves 20–30%), a clear permissions concept and a realistic migration strategy.

"The opening moves decide the game."

Key Takeaway: Strategy first. Governance scales.

UNO – Expect the Unexpected

Surprises are part of every migration: hidden technical debt, last-minute changes from stakeholders, app incompatibilities, data quality issues (duplicate users, broken links, corrupt attachments).

"Calling UNO doesn't protect you from a +4."

Key Takeaway: Flexibility and good time management make the difference.

RISK – Stakeholder Management

User adoption is the bottleneck. Change resistance must be addressed proactively – with stakeholder mapping, targeted communication and a champions programme.

"Allies win battles."

Key Takeaway: Without clear involvement, there is no buy-in.

JENGA – Apps & Dependencies

One wrong move destabilises the entire instance. Critical areas: too many apps and add-ons without verified cloud compatibility, hidden dependencies (automation rules, ScriptRunner, workflows), data migration risks for custom fields and attachments, and undocumented system integrations.

"The wrong piece brings everything down."

Key Takeaway: Know your dependencies. Manage your critical paths.

The Migration Roadmap

Conclusion

The Atlassian Finance User Forum Spring 2026 made it clear: the cloud is no longer a future vision for regulated financial institutions – it is lived reality. The combination of an AI-native platform, FINMA-compliant infrastructure and proven migration expertise makes the transition more achievable than ever – provided you approach it in a structured and strategic way.

We are already looking forward to the next Atlassian Finance User Forum in autumn. In the meantime, we are happy to answer any questions about cloud migration, governance and Atlassian.