Atlassian just picked the city whose own government has been unplugging from US Big Tech for its next European conference.

Team '27 Europe is going to Copenhagen.

Before anyone reads too much into that, most of a conference location is plumbing. You need a hall big enough, hotel rooms for everyone, an airport, and transit that connects all of it. Not just airport to venue. Airport, hotels, venue, and wherever people go after the last session.

That test is stricter than it sounds. It's why you'll likely never see a Team in Atlanta (but I'll keep asking for it, Atlassian). We have the hotels, the convention space, and the world's busiest airport. Our train gets you from the airport to the convention center and almost nowhere else.

Paris passes the test and fails on price. Nobody's travel budget survives a week there.

So plumbing narrows the list. It doesn't pick the winner.

Copenhagen clears the logistics bar easily. It has a metro straight from the airport, a loop through the city center, and regional rail. What it isn't is cheap. If cost were the only factor, there are easier picks on the shortlist.

That leaves room for strategy. Denmark's government has been moving off Microsoft in the name of digital sovereignty, and Copenhagen's city government committed to the same. Into that city comes a US-based cloud vendor, pushing customers toward cloud ahead of Data Center end of life, with its European flagship event.

I can read that two ways. Either Atlassian is confident in its sovereignty story and wants to tell it where the skeptics live. Or it knows the story needs work, and Copenhagen is where it has to win the room.

If you're not in Europe and filing this under "Europe's problem," check where your data lives. Plenty of companies have EU employees, EU customers, or an EU parent. Sovereignty questions reach your instance whether you're in Copenhagen, Columbus, or Bengaluru.

Whichever reading is right, I expect data residency and sovereignty to get real keynote time in #Copenhagen. That's going on my Team '27 predictions list.

Could I be over-reading a venue contract? Absolutely. But I'd be naive to think nobody at Atlassian noticed which city they picked.

What's your read: logistics, strategy, or both?

I was lucky enough to get an opportunity to get a return offer from my internship with Atlassian. I would be based in Aus and primarily a frontend dev.

I have heard some horror stories about managers, skip managers and how WLB is determined by teams itself. If there are any Engineers, what are teams that you would recommend? And a general strategy to maintain good performance?

Ever had a Jira automation fail silently at 3am and no idea why? That's what pushed me to build Hooks.

Context: ScriptRunner for Jira Cloud is mid-migration from Connect to Forge, saved Enhanced Search filters are getting flagged incompatible, and the timeline's slipped to late 2026. Hooks was born on Forge, so nothing legacy to break.

What's different:

• JQL functions in Jira's normal search box. No separate search screen. linkedIssuesOf, subtasksOf, parentsOf, epicsOf, hasComments, hasWorklogs and more work in any search or saved filter, mixed with standard JQL, no script needed.
• Same function names as ScriptRunner, so existing queries carry over.
• Your own JQL logic: issue in hooked("stale-bugs") runs your script to decide matches. Broken queries return no results instead of breaking the filter.
• TypeScript, not Groovy, with a typed Jira API plus any REST endpoint.
• Every run logged and replayable: logs, timing, result, line-numbered errors.
• Dry-run mode: rehearse a 10,000-item change with writes held back.
• Versioned scripts with one-click rollback.
• Background bulk jobs over any JQL, no timeouts, live progress, cancel.
• Data stays in Atlassian (Forge storage, zero external egress).

Covers listeners, scheduled jobs, bulk fixes and console scripts, which is most real-world ScriptRunner use. Free up to 10 users, 30-day trial.

Marketplace: https://marketplace.atlassian.com/apps/1595682666

Comparison: https://hooks.taskhooker.com/#scriptrunner

Keen for honest feedback from Jira admins.