Atlassian Data Center price changes effective February 2026: what you need to know If you are running Atlassian products in a Data Center environment, February 17, 2026 marks a significant date for your budget planning. Atlassian has announced pricing updates that will increase costs for Jira, Confluence, and Jira Service Management Data Center deployments by 15% or more. This is not just a routine price adjustment. It arrives alongside Atlassian's broader strategy to transit
When you deploy Confluence, you aren't just installing software—you are trying to prevent organisational chaos. Yet, most IT managers inherit or build Confluence instances that quickly devolve into sprawling, unsearchable junk drawers that teams eventually stop trusting. If your teams are treating Confluence like a glorified shared file drive instead of a structured knowledge management system, your architecture is broken. This guide is built specifically for the IT manager o
Jira is excellent at what it was born to do. Track work. Move issues. Keep a record of decisions. Ship. But the moment you try to plan across time, real time with dates, dependencies, milestones, competing priorities, people going on leave, and a stakeholder asking, “So when will it be done?”… teams start feeling friction. Because boards are not timelines. A Scrum board shows work in progress, while a Kanban board shows work flowing. Both aid daily execution. But neither is a
Atlassian Data Center price changes effective February 2026: what you need to know If you are running Atlassian products in a Data Center environment, February 17, 2026 marks a significant date for your budget planning. Atlassian has announced pricing updates that will increase costs for Jira, Confluence, and Jira Service Management Data Center deployments by 15% or more. This is not just a routine price adjustment. It arrives alongside Atlassian's broader strategy to transit
When you deploy Confluence, you aren't just installing software—you are trying to prevent organisational chaos. Yet, most IT managers inherit or build Confluence instances that quickly devolve into sprawling, unsearchable junk drawers that teams eventually stop trusting. If your teams are treating Confluence like a glorified shared file drive instead of a structured knowledge management system, your architecture is broken. This guide is built specifically for the IT manager o
Jira is excellent at what it was born to do. Track work. Move issues. Keep a record of decisions. Ship. But the moment you try to plan across time, real time with dates, dependencies, milestones, competing priorities, people going on leave, and a stakeholder asking, “So when will it be done?”… teams start feeling friction. Because boards are not timelines. A Scrum board shows work in progress, while a Kanban board shows work flowing. Both aid daily execution. But neither is a
Jira automation in 2026 is not the cute little “when issue created, assign to Bob” thing most of us started with. It’s bigger now. Not necessarily more complicated, but definitely more connected. Teams are automating across Jira Software, Jira Service Management (JSM), Confluence, and then the stuff that actually runs the business outside Atlassian. ERP. Microsoft 365. Identity. Monitoring. Asset systems. The whole messy stack. So let’s set expectations early. When I say “wor
When an organisation decides to implement Confluence, the decision rarely lands with a project manager or a department head. It lands with the IT manager or system administrator who has to make it work — who has to select the right licence, design the space architecture, configure permissions, and then somehow get a hundred different people using the same platform consistently. This guide exists for that person. It covers the foundational decisions that determine whether a Co
Part A of this series covered Confluence's core architecture, licensing decisions, and the space design choices that determine whether a deployment scales or fragments. This second part moves from architecture to operation — the specific configuration decisions that IT managers and Confluence administrators make daily. How pages are created, how drafts and version control work, how templates should be governed, how permissions cascade through groups and individuals, how space