Blogs

In 2024, I shared my thoughts on whether Jira professionals should invest their time in learning Jira Data Center and ScriptRunner for Jira. Back then, my advice was influenced by Atlassian’s strong push toward Jira Cloud, which they’ve clearly stated is their long-term focus.But as of mid-2025, the situation has evolved — and so has my advice.The State of Jira Data Center in 2025Atlassian has not announced any end-of-life date for Jira Data Center. In fact, they’re still:

Reopening old bugs might seem like a quick fix, but in reality, it can cause confusion, mess up reports, and create long-term issues in bug tracking. In this post, we’ll explore why reopening old issues is a common mistake, why it happens, and the better alternative to manage recurring bugs.The Common ScenarioIn many large companies, products are released in multiple versions — for example, v3.2.1, v3.3, and so on. Each version:

Here’s a quick rundown of some important updates from the Atlassian ecosystem this week. These changes may seem small individually, but together they reflect how Atlassian is steadily improving its tools — and why we, as Jira admins and consultants, need to stay on top of them.

Are you a Jira administrator dreaming of a career switch? The world of Jira consulting might be calling your name! It's a field that offers not only competitive compensation globally but also significant respect and influence, as consultants are often highly valued for their expertise. If you've ever considered this path, now might be the time to explore it. The Foundational Skill: Jira Administration 

Recently, on June 22nd, Atlassian made an announcement that has stirred up quite a bit of discussion in the Jira community: Jira "Projects" are being renamed to "Spaces." As a consultant deeply ingrained in the Atlassian ecosystem, this news, frankly, leaves me unhappy. While there might be a grander vision behind it, the immediate impact, in my opinion, will be confusion. What is a "Project" Anyway? (And How Jira Used It) 

Recently, a potential customer reached out, frustrated and vocal about their Jira experience. Their core complaint? Jira wasn't living up to the promise that it could be used for any use case and solve all problems. Specifically, they were attempting to leverage Jira as a CRM – a system fundamentally designed for managing customer data, typically handled by specialized tools like Salesforce.

As Jira and Confluence support providers, we frequently encounter a common, yet problematic, scenario: users who are accustomed to an "ad hoc" style of support. This often stems from well-intentioned administrators who, in an effort to be helpful, inadvertently establish practices that can lead to chaos and inconsistency within the Jira instance. The Slippery Slope of Uncontrolled Customization 

This blog post discusses configuration management in Jira.Jira, as a tool, was never fundamentally designed to support the seamless movement of configurations from one environment to another. This is a common misconception, but unfortunately, it's not truly the case in practice. The Illusion of Simple Configuration Changes 

As consultants deeply entrenched in the world of Jira, we often find ourselves pondering the future of Jira Data Center. While Atlassian has been steering users towards Jira Cloud, and the eventual "demise" of Data Center is a whispered possibility (though hopefully far off!), we still have ample time – perhaps five-ish years – to leverage its capabilities. And for many of us, Jira Data Center is where we earn our living.

Goodbye to "Manage Apps," Hello to "Connected Apps"The first major update revolves around how we manage apps within Jira and Confluence. Atlassian had announced last year that the traditional "Manage apps" section would be transitioning to a new area called "Connected apps."