Real Atlassian solutions to real problems — no fluff, no SEO spam.
A customer changes email domain and starts appearing twice in the reporter picker. Removing them from the project provably cannot fix it, the query that finds their tickets stays silent when it fails, and the reassign that clears them reports the wrong reason for refusing.
A blocks link in Jira records a relationship. On Free and Standard it reschedules nothing. Here's the engine we put behind it, the required-start rule that's easy to get subtly wrong, and what it still can't do.
App passwords are removed on 28 July 2026, and in the final week they were already dark 20 hours out of every 24. Here is the failure signature, the three different usernames nobody can keep straight, why swapping in a token often changes nothing, and the reason almost no team can tell you who is still affected.
After enough Data Center to Cloud migrations, you develop an instinct for when things are about to go sideways. It's never the core data — Jira issues, Confluence pages, user accounts — that breaks the project. It's the apps. Specifically, it's the moment you realize the vendor doesn't have an answer either, and your client's deadline doesn't care.
After 10+ Data Center to Cloud migrations, here's what nobody tells you: they're imperfect by necessity, not by design. Waiting for perfection is the single most expensive mistake an organization can make — and I've watched it happen in real time.
