It started, as these things always do, with a number that didn’t make sense.

When the IT director at a mid-sized energy company first called us, she wasn’t worried about ghosts. She was worried about budget. “We’re paying for almost 500 Jira licenses,” she said, “but I swear half these people don’t even use it.” She could hear the wind howling down the empty digital hallways.

And that fear was not paranoia. Industry-wide, 53% of IT teams report challenges gaining or maintaining complete visibility of their technology investments. In other words, this director was describing the real problem hiding in plain sight for more than half of IT teams: they cannot confidently see what they own, what is being used, or where spend is quietly leaking away.

Suit up, Health Check Crew

So our health check team put on our protective gear and dove into their Atlassian instance. Within the first hour, we found them: 255 user accounts that hadn’t logged in for over three months. Not a single click. Not a single comment. Just names on a list, silently draining the budget like something feeding in the dark.

But that was only the first floor of the haunted house. 🏚️

We kept digging. Their Jira and Confluence environments were running on completely separate Atlassian sites, split apart like two halves of a broken mirror. There was no identity provider connecting them. Password policies? Weak, with no expiry dates. Every credential was a door left unlocked in a building no one was watching.

Fifty-five percent of their licenses were ghosts. 👻 The security posture was one bad day away from a breach. And the team running it had inherited the setup from someone who left years ago, and had been holding it together with duct tape and determination ever since.

Here’s the thing about ghosts in your system: they don’t rattle chains or slam doors. They just cost you money, quietly, month after month, while the real dangers hide in the configuration nobody has looked at since the last admin left.

Our health check didn’t stop at a flashing light on a Ghost-finder-ometer, 🚨(or whatever it’s called). We then gave their team a flashlight, a map, and a plan to reclaim over half their licensing costs while closing security gaps that could have turned into front-page incidents. And then we walked through the house with them, being an extra support for the good-riddance-ghosts initiative.

If your Atlassian instance has been running on autopilot, chances are something is lurking inside. The question isn’t whether you have ghosts, but how many and what they cost you.

What’s lurking in your instance? A health check will show you.