Atlassian Team '26 Europe
Amsterdam, October 6-8, 2026
Table of Contents
Overview
Atlassian Team '26 Europe. European counterpart to Team '26 (Atlassian's US flagship). Framing: Unleash your teams and their agents. Everyone. Working on the right things. In Jira, teams and AI agents plan, execute, and deliver outcomes together.
The published agenda is a scaffold — three days of expo floor and "breakout & learning sessions" bookended by keynotes. Named sessions (Founder Keynote, Rovo Happy Hour, Closing Keynote, Bash) are the only programmatic anchors so far; the track/session catalog under each "Breakout & learning sessions" band is not yet exposed on the agenda index.
Logistics
- When: October 6-8, 2026
- Where: Amsterdam, Netherlands (venue not published on the agenda index; the registration flow is the source of truth)
- Site: https://team.atlassian.com/europe
- Agenda: https://events.atlassian.com/teameurope/agenda (Swoogo-hosted; session slugs of the form
/teameurope/session/<id>/<slug>) - Format: three-day in-person conference
Schedule
Day 1 — Tuesday, 6 October
| Time | Session |
|---|---|
| 10:00 AM – 6:00 PM | Breakout & learning sessions |
| 1:00 PM – 6:00 PM | Expo open |
| 4:00 PM – 6:00 PM | Welcome Reception |
Day 2 — Wednesday, 7 October
| Time | Session |
|---|---|
| 8:00 AM – 6:00 PM | Expo open |
| 9:00 AM – 10:30 AM | Founder Keynote |
| 11:00 AM – 4:00 PM | Breakout & learning sessions |
| 4:00 PM – 6:00 PM | Rovo Happy Hour |
Day 3 — Thursday, 8 October
| Time | Session |
|---|---|
| 8:00 AM – 3:00 PM | Expo open |
| 8:30 AM – 2:30 PM | Breakout & learning sessions |
| 3:00 PM – 4:00 PM | Closing Keynote |
| 5:00 PM – 8:00 PM | Bash |
Shape
Three days, no visible parallel-track structure yet on the agenda index — everything not a keynote or reception collapses into a "Breakout & learning sessions" band. That's a Swoogo scaffold, not the final program: the individual session-detail pages exist (they hydrate client-side) but haven't been pulled into the top-level agenda.
The programmatic anchors:
- Founder Keynote — Wed 9:00. Scott Farquhar + Mike Cannon-Brookes historically; roster not yet confirmed for Europe.
- Rovo Happy Hour — Wed 4:00 PM. Rovo is Atlassian's agent product; the fact it gets its own reception is a positioning signal.
- Closing Keynote — Thu 3:00 PM.
- Bash — Thu 5:00 PM. Party/networking closer.
Not yet captured
Refresh once the JS-rendered session catalog under each "Breakout" band becomes indexable:
[ ]Venue name + address (registration flow only)[ ]Breakout session catalog + speakers per day[ ]Track structure (product / customer / partner / etc.)[ ]Pricing tiers + early-bird cutoff date[ ]Sister-event schedule (Team '26 US dates)
Instrumentation observation
The events site runs Statsig client-side (sdkType: "java-server",
sdkVersion: 3.1.3, hash_used: "djb2") with analyticsAnonymousId
as the primary bucketing id and atlCohort as a custom attribute.
Consent is managed by OneTrust ("US Generic" template, GPC + DNT
honored, four cookie tiers).
Adjacent to the site's own gate SDK — see experiments for the shape we ended up copying (djb2 + static-file "server", no upstream call). The Statsig payload from this event's agenda page was the reference model.
Scheduling conflicts
Direct conflict with SPLASH/ISSTA 2026 in Oakland (Oct 6-8), including both workshops we're tracking there:
- SpecOps 2026 (Oct 6-8, Oakland)
- EXPRESS 2026 (Oct 3-9, Oakland)
Pick one continent for that week.
Adjacencies to current work
- Agent + human workflow in Jira: adjacent to the site's agent-context and durable-execution threads. If they publish keynote video, capture the framing.
- Atlassian MCP: recent Atlassian MCP release is likely showcased; relevant to the MCP-connector work.
- Beads / bd: personal task-tracking is bd-based, not Jira; Atlassian's framing of "AI agents in Jira" is worth reading as an alternative model even if unadopted.
TODO
[ ]Fill in venue + agenda + speakers once page hydrates or a schedule PDF drops.[ ]Decide Amsterdam vs SPLASH/ISSTA Oakland for that week.[ ]Track early-bird deadline (if considering registration).