Your weekly source for tips, tricks, and how-to's to get the most from your Atlassian tools
Nine ACP exams down, a tenth on the calendar, and I still tell people to go for it. When an agent can look up any answer in three seconds, are Atlassian certs still worth it? I think the judgment they build matters more than ever. Here’s what studying for one actually gets you.
Atlassian’s agentic Jira launch isn’t a new strategy — it’s the Team ’26 manifesto shipping as receipts. Here’s what it actually changes for admins and architects.
Is it actually harder to land an Atlassian admin job right now, or does it just feel that way from inside a job search? Three forces are squeezing the market at once: Atlassian’s own AI-attributed layoffs, Rovo quietly absorbing tier-one work, and cloud consolidation shrinking the per-org admin footprint. Only two are about AI, and the third might be the most permanent. Here’s the breakdown, and what’s still landing interviews.
A few years ago I built a Scrum board out of wood and torches in Valheim. Carved columns: To Do,…
A new Atlassian Project field is being added to all your Jira screens in July — automatically. Here’s what it does, why the community is already reacting, and how to remove it.
94% of workers are using AI. The honest ones are being penalized for it. Atlassian’s own research lab just put it in writing. Here’s what it means for practitioners.
Atlassian Connect Phase 2 is already active — your apps can no longer grow. Here’s what it means for your instance and what to ask your vendors.
Atlassian’s upcoming field schemes replace Jira’s three-layer field configuration system. Here’s what’s actually changing, what it means for experienced admins, and how to prepare before Q3 2026.
Managing serious illness is a literal project management job. Here’s my actual backlog — and what happens to people who don’t have these skills.
Most Jira migrations don’t go sideways because the tool fails.
They go sideways because expectations were wrong.
There’s a persistent assumption that the Jira Cloud Migration Assistant simply copies your instance from Data Center into Cloud. Same structure. Same behavior. Different hosting model.
But that’s not what happens.
JCMA translates. And translation always involves interpretation.
Workflows may look similar but behave differently. Permissions may map correctly but feel different to users. Fields may exist but show up in unexpected contexts. None of that means the migration failed — it means the environments aren’t mirrors.
In this week’s article, I break down what the migration assistant actually does, what it absolutely does not do, and why your first migration run should be treated as a diagnostic exercise — not a finish line.
If you’re planning a move to Cloud, understanding this distinction changes everything.
The Jira Guy 