Jira disaster recovery tells you how to get back to green. It doesn’t tell you what keeps running meanwhile. Seven failure modes, and a template.
Tag: jira
Are Certifications Worth It in the AI Age? I’m Going for the Full Set.
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 Dropped New AI Dev Tools — Let’s Talk About It
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.
I Built a Scrum Board in Valheim, and the Embarrassing Part Is It Works
A few years ago I built a Scrum board out of wood and torches in Valheim. Carved columns: To Do, … More
Atlassian’s Project Field in Jira: What Admins Must Know
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.
Your Atlassian Apps Already Hit a Ceiling. Here’s What to Do About It.
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.
Field Schemes: The End of Jira’s Three-Layer Field Problem
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.
Six Impossible Things Before Breakfast
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.
Before We Migrate: Understanding the Impacts of Jira Cloud Migration Assistant
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.
Before You Migrate Anything: Understand What Jira Is Really Being Used For
Most Jira migrations don’t struggle because the data won’t move.
They struggle because nobody stopped to ask what the data actually means first.
Every admin thinks they know their instance. And honestly, they probably know it better than anyone else in the company. But knowing how Jira is configured isn’t the same as knowing how it’s really being used. Old projects stick around. Fields collect dust. Workflows solve problems nobody remembers having. Then the day you move to Cloud, all of that becomes real again — in front of users who now assume you intended it.
Before choosing tools, timelines, or even strategy, there’s a much simpler (and much harder) step: figuring out what matters and what just survived long enough to look important.
This week’s article is about replacing assumptions with evidence — and why that changes the entire migration conversation.
The Jira Guy 