This case study examines how our organization evaluated and selected the appropriate platforms to manage support operations, project tracking, and knowledge management. While we continue to leverage Jira and Confluence as our primary systems for project management and development tracking, we ultimately selected HaloITSM as our integrated support and knowledge management solution.

Although Confluence provided strong documentation capabilities and Jira offered strong project tracking functionality, HaloITSM better addressed our specific operational need: seamless integration between ticket inception, ticket resolution management (Levels 1–3), and knowledge creation within a controlled support environment.

This decision highlights a key lesson: product selection should not be based solely on feature superiority, but on how effectively a solution fills the operational gap within a specific use case.

Our organization operates with two distinct but interrelated technology functions:

1. Support Operations (Level 1–3 tickets)

2. Project Management and Development Tracking

To support these functions, we use:

▢ HaloITSM as our support management system

▢ Jira for project and development tracking

▢ Confluence for documentation and non-support knowledge management

While each system offers strengths, aligning them with operational requirements presented both opportunities and challenges.

As daily support requests increased, we faced several operational pressures:

▢ Efficient tracking and resolution of Level 1–3 support tickets

▢ Clear communication and status visibility for clients

▢ Creation of reusable documentation from resolved tickets

▢ Maintaining strict control over confidential client data

▢ Avoiding fragmentation between ticket creation and knowledge documentation

Initially, we evaluated whether Jira and Confluence could fully support both project and support workflows. However, we discovered that although these tools were strong for structured project environments, they did not provide the level of integration required for support ticket lifecycle management.

Additionally, while HaloITSM offered powerful capabilities, we encountered challenges in leveraging its full potential while ensuring client confidentiality and data segmentation requirements were maintained. Balancing automation with compliance became a key consideration in our decision-making process.

1. HaloITSM (Support System of Record)

HaloITSM serves as our primary IT service management (ITSM) platform. Its core advantages include:

▢ Native ticket lifecycle management

▢ Integration between ticket creation and resolution documentation

▢ Automated knowledge article generation

▢ Linking related incidents and historical issues

▢ Structured Level 1–3 escalation handling

Strengths Identified

▢ Automatic creation of knowledge articles upon ticket resolution

▢ Intelligent linking of recurring issues

▢ Centralized support operations workflow

▢ Improved client communication within the same system

Challenges Identified

▢ Limitations in knowledge base configurability compared to Confluence

▢ The need to carefully design processes to maintain client confidentiality

▢ Some constraints when attempting to maximize automation without compromising data governance

Despite these challenges, HaloITSM provided something critical: direct integration between new ticket inception and ticket resolution documentation within the same support environment.

2. Jira and Confluence (Project & Documentation Systems)

We continue to use Jira and Confluence as our systems of choice for:

▢ Agile development tracking

▢ Sprint planning

▢ Roadmapping

▢ Internal documentation

▢ Cross-team collaboration

▢ Non-support knowledge repositories

Confluence

Confluence remains the stronger documentation platform in terms of:

▢ Page structure and hierarchy

▢ Template flexibility

▢ Rich formatting and customization

▢ Robust configuration capabilities

For large-scale documentation, internal process manuals, and development knowledge, Confluence is unmatched in usability and configurability.

Jira

Jira provides:

▢ Strong issue tracking

▢ Agile workflow management

▢ Integration with development pipelines

▢ Clear visibility across technical and non-technical stakeholders

However, using Jira and Confluence for support ticket resolution presented limitations:

▢ Documentation had to be created manually in Confluence

▢ Linking ticket inception with knowledge documentation required extra steps

▢ Email and client communication often occurred outside the platform

▢ Resolution knowledge was not automatically embedded into the support lifecycle

Although Confluence was clearly the more powerful documentation tool, our primary goal was not advanced configuration or robust page architecture.

Our objective was to integrate ticket resolution management directly with new ticket creation at inception, ensuring efficient handling of Level 1–3 support tickets.

For this specific operational need, HaloITSM’s weaker knowledge base was strategically superior because:

▢ It eliminated system switching

▢ It reduced manual documentation overhead

▢ It ensured knowledge creation was embedded within the support workflow

▢ It provided tighter integration between incident resolution and reusable knowledge

We accepted trade-offs in configurability in exchange for improved workflow integration.

1. Improved Support Efficiency

Embedding knowledge generation directly into the support ticket lifecycle reduced time spent on manual documentation and improved resolution times for recurring issues.

2. Better Knowledge Reuse

By linking related tickets and surfacing historical solutions, HaloITSM improved first-response effectiveness, particularly at Level 1.

3. Controlled Confidentiality

While leveraging HaloITSM’s capabilities required careful governance, the centralized support structure allowed us to better control how client-sensitive information was documented and accessed.

4. Continued Excellence in Project Management

Jira and Confluence remain integral to our organization for non-support operations. Their strengths in development tracking, sprint management, and structured documentation continue to support broader organizational goals.

Key Insight: Capability vs. Gap

This case study demonstrates a critical principle in enterprise tool selection:

The best product is not always the one with the most features — it is the one that most effectively fills the operational gap.

▢ Confluence is the stronger documentation platform.

▢ Jira is a powerful project management tool.

▢ HaloITSM’s knowledge base is less configurable.

However, for Level 1–3 support operations requiring seamless integration between ticket creation and resolution documentation, HaloITSM filled the gap more effectively.

The decision was not about selecting the “better” product overall. It was about selecting the right product for the right function.