Case management for municipalities: why more are choosing Jira Service Management

It often starts with a deceptively simple question at a management meeting: "How many case management systems do we actually have?" The answer tends to surprise people. One system for IT support, one for HR, one for citizen-reported issues, and a spreadsheet that someone in facilities built in 2017 that nobody dares to touch. Four systems, four logins, four licence costs – and zero overview.

When contracts expire, budgets are reviewed and new digitalisation goals need to be put into practice, case management often rises to the top of the agenda. In this guide we go through the requirements a municipality should set for a modern case management system – and why Jira Service Management (JSM) is increasingly showing up as an option.

What is case management in a municipality?

Case management is about receiving, registering, assigning, resolving and following up requests – whether they come from a citizen, an employee or an internal system. In a municipality it spans very different operations:

• IT support: incidents, access rights, orders for hardware and accounts.

• HR and internal services: onboarding, employment questions, internal facility services.

• Citizen services: questions, feedback and issue reports (e.g. streets, parks, lighting).

• Cross-departmental processes: cases that need to move between departments with full traceability.

What they all have in common is the need for traceability, clear ownership, reasonable response times (SLAs) and the ability to track volumes and bottlenecks. This is where older systems often fall short.

Common problems with older case management systems

Most public organisations are stuck with systems that were procured a long time ago. The symptoms are familiar:

• "Our current system is from the 2010s and nobody really knows how it all fits together."

• "We need better self-service for citizens – but the portal we have is neither mobile-friendly nor accessible."

• "We want one system that IT, HR and citizen services can all use, not three separate ones."

• "ServiceNow feels too expensive and too big for us."

• "We have to meet WCAG 2.1 AA – and we don't know whether our system can."

This is not primarily a technical problem. It is a governance and cost problem. Every extra system means an extra integration, an extra vendor relationship and an extra point where compliance can fail. The older the systems are, the harder it becomes to justify a multi-million-kronor project without clear reference cases from other municipalities.

Requirements to start from when choosing a case management system

Whatever system you choose, the evaluation should start from the same basic requirements. A useful checklist:

• Data protection and GDPR: Where is data stored? Can data be kept within the EU? Are there data processing agreements and support for DPIAs?

• Accessibility (WCAG 2.1 AA): Do both the agent interface and the citizen portal meet the legal accessibility requirements?

• Procurement (the Swedish Public Procurement Act, LOU): Can the system be introduced through a direct award, an existing framework agreement, or does a new procurement need to be run?

• Integrations: Open APIs to e-services, identity (BankID/SITHS), finance systems and other line-of-business systems.

• Reporting and follow-up: SLA tracking, volumes, response times and a basis for continuous improvement.

• Total cost: Licence, implementation and operations over the contract period – not just the list price.

What is Jira Service Management – and why is it mentioned more and more?

Many people react instinctively: "Jira? Isn't that a tool for developers?" Jira Software is. But Jira Service Management is a separate product, built specifically for service management – that is, case management. It is used by IT departments, HR, facilities, customer service and citizen services, and is based on established ITIL principles for incident, problem and change management.

The reason JSM is mentioned more and more in the public sector is a combination of three things maturing at the same time: stricter GDPR and accessibility requirements, pressure to lower licence costs, and the option to eventually add an AI layer on top of the case flow.

1. One platform for several types of cases

The biggest gain is consolidation. With JSM, IT support, HR cases, citizen cases and issue reports can be handled in the same system – with separate service projects, their own queues and their own SLAs, but a shared platform and knowledge base. In practice a municipality can merge several tools into one and get a single view of case volumes, response times and bottlenecks.

2. Support for GDPR and accessibility requirements

This is often the deciding point. In its reports, AI Sweden points to GDPR uncertainty as a primary blocker for digitalisation and AI adoption in the Swedish public sector – not the technology itself, but the uncertainty about where data ends up.

JSM Cloud can be configured with EU data residency (data centres in Frankfurt and Dublin, among others), making it possible to keep primary data within the EU. The customer portal can also be made WCAG 2.1 AA compliant. It is important to be clear: compliance is not "done" automatically – it still requires configuration, documentation, a DPIA, data processing agreements and routines. As a Swedish supplier we help with exactly that documentation, which is often what takes time in an LOU process.

3. Often a lower licence cost than large enterprise platforms

Many municipalities assume that a "real" case management system has to cost as much as the largest enterprise platforms. It doesn't have to. JSM can often deliver a significantly lower licence cost per agent than larger ITSM suites, with functionality that covers most public-sector needs. The actual costs depend on the number of agents, licence tier and add-ons, so always compare against a current quote for your volume.

JSM compared to traditional ITSM systems

A simplified comparison on the points that are most often decisive for a municipality:

For an organisation with 30–50 agents, the difference in total cost can determine whether the project becomes a budget decision or a larger procurement project. But cost is only one of several factors – functionality, integrations and operations weigh at least as heavily.

When is JSM a good fit – and when is it not?

An honest picture makes the decision easier:

JSM is a good fit when:

• You want to consolidate several case types (IT, HR, citizen services) on one platform.

• You value open APIs and want to be able to integrate and automate freely.

• Licence cost and time to go live are important factors.

• You want to be able to start small with a pilot and grow step by step.

JSM is less suitable when:

• You already have a large, deeply integrated enterprise platform that works well and was just renewed.

• The operation requires highly specialised industry modules that a niche vendor covers better.

• There is no internal willingness to maintain configuration – then you need a clear operations partner from the start.

How a municipality can start – with a focused pilot

Smart Source helps municipalities and public organisations evaluate, configure and implement Jira Service Management. Our advice is almost always to start small: a pilot within, for example, IT support or internal services, where the value can be proven quickly and without major risk. From there you build further with more departments, integrations and – when the time is right – AI support.

We deliver the whole package: data migration, configuration of service projects and SLAs, WCAG adaptation of the portal, compliance documentation, training and a transparent, fixed operating cost. The idea is simple: you should be able to focus on your citizens and your cases, not on maintaining a system.

Checklist before switching case management system

• How many case management systems do we have today, and what do they cost together?

• What are our requirements for GDPR, EU data residency and DPIA?

• Do both the agent interface and the citizen portal meet WCAG 2.1 AA?

• Can a new system be introduced via a direct award or an existing framework agreement?

• Which integrations are a must (identity, e-services, finance)?

• What reporting and follow-up do we need to steer operations?

• Can we start with a focused pilot and evaluate before we scale?

And further ahead: JSM + AI

Once the foundation is in place, JSM's open API opens the door to an AI layer on top of the case flow, via MCP (Model Context Protocol) – the same technology we have used in four production environments (Eventry, Umbraco, Kimai and Krayin CRM). Concretely, an agent can ask an AI assistant to summarise a long case, suggest replies based on the knowledge base, or categorise and prioritise incoming cases. For an organisation worried about data sharing, the model can be run locally – for example with Ollama running Llama 3 or Mistral on a server in Sweden – so that no case content leaves the organisation. AI, however, is a step you take once the foundation is solid, not the first thing you need to solve.

Summary

More and more Swedish municipalities are looking at Jira Service Management because it addresses four recurring needs: better overview through a shared platform, support for GDPR and accessibility requirements, a more manageable licence cost, and a path forward towards AI support. What previously required several systems and a large project can today often start as a focused pilot of a few weeks – but the decision should always rest on a proper review of your own requirements and flows.

Book a free review

Wondering about your case management system? Book a free review of your current case flow. We help you identify which systems, flows and costs can be consolidated – and show what a focused JSM pilot could look like for your specific organisation. Book a time here.