Get Znuny professionally installed
Avoid trial and error in production: Softoft handles turnkey Znuny deployment, Docker or bare-metal setup, security hardening, and baseline configuration.
Introduction to Znuny
Welcome to the Znuny Community Docs! This guide will help you get started with Znuny – the open-source ticket system for professional service management.
What is Znuny?
Section titled “What is Znuny?”Znuny is a powerful, flexible ticket system for managing customer inquiries, support tickets, and service processes. It offers:
- Structured ticket management – Capture, categorize, and prioritize requests efficiently
- Automation – Reduce manual work through rules, processes, and generic agents
- Dynamic fields – Customize forms and data fields to your requirements
- REST API & Web Services – Seamlessly integrate Znuny into your existing IT landscape
- AI integration – Leverage artificial intelligence for automatic categorization and text analysis
Who is this documentation for?
Section titled “Who is this documentation for?”| Target audience | Recommended starting points |
|---|---|
| Agents | Ticket basics – Ticket creation and editing |
| Administrators | System administration – Configuration and maintenance |
| Developers | Plugin development · Add-ons on OpenITSMHub |
Quick Start
Section titled “Quick Start”- Installation: Deploy Znuny with Docker Compose (Ubuntu · Debian) or follow the official Linux guide
- First login: Sign in as
root@localhostwith the setup password - Basic configuration: Adjust system settings, queues, and users
- Create a ticket: Create a first test ticket to explore the interface
Key Concepts
Section titled “Key Concepts”Tickets
Section titled “Tickets”The heart of Znuny. Each ticket represents a customer inquiry, incident, or task with a unique ticket number, status, priority, and assigned agent.
Queues
Section titled “Queues”Organizational units for tickets (e.g., Support, Sales, Technical). Tickets are sorted into queues and can be moved between them.
Dynamic Fields
Section titled “Dynamic Fields”Additional data fields that you define yourself – for custom information like customer numbers, product versions, or internal codes.
Processes
Section titled “Processes”Visually modeled workflows for complex procedures with defined activities, transitions, and conditions.
Next Steps
Section titled “Next Steps”- Configure dynamic fields – Customize your ticket forms
- System administration – Learn the essential admin functions
- AI integration – Discover the possibilities of artificial intelligence
- Znuny add-ons – Plugins and extensions on OpenITSMHub
- Znuny REST API – Integrations and automation
Frequently asked questions
What is Znuny and what are its main capabilities?
Znuny is a robust, open-source ticket system designed for professional service management. It originated as a continuation of the OTRS Community Edition after its maintenance was discontinued in 2020, providing ongoing bugfixes and security updates. Its core capabilities include structured ticket management for efficient request handling, powerful automation features to reduce manual workload through rules and generic agents, and highly customizable dynamic fields that allow users to tailor forms and data fields to specific requirements. Furthermore, Znuny offers a comprehensive REST API and web services for seamless integration into existing IT infrastructures, and it supports AI integration for advanced functionalities like automatic categorization and text analysis, enhancing efficiency and responsiveness in customer service operations.
Quellen:
How do I get started with Znuny after installation?
After successfully installing Znuny, either via Docker Compose or by following the official Linux guide for distributions like Ubuntu or Debian, the first step is to perform your initial login. You should sign in as root@localhost using the setup password provided during the installation process. Following this, it's crucial to proceed with the basic configuration, which involves adjusting essential system settings, setting up queues to organize tickets (e.g., Support, Sales), and configuring user accounts. Finally, to familiarize yourself with the interface and workflow, you should create a first test ticket. This hands-on approach helps in understanding how tickets are managed within the system.
Quellen:
What are the fundamental concepts in Znuny that I should understand?
To effectively use Znuny, it's important to grasp its fundamental concepts. Tickets are at the heart of the system, representing every customer inquiry, incident, or task with a unique number, status, priority, and an assigned agent. Queues serve as organizational units, categorizing tickets (e.g., for different departments like Support or Sales) and allowing them to be moved between relevant teams. Dynamic Fields are highly customizable additional data fields that you can define yourself to capture specific information, such as customer numbers, product versions, or internal codes, tailoring ticket forms to your needs. Lastly, Processes enable the visual modeling of complex workflows, defining specific activities, transitions, and conditions to guide users through structured procedures.
Quellen:
How can I customize and extend Znuny's functionality?
Znuny offers several powerful ways to customize and extend its functionality to meet specific organizational needs. You can configure dynamic fields to tailor your ticket forms, adding custom information like customer numbers or product versions, which significantly enhances data capture and organization. For core system management, system administration allows you to learn and apply essential administrative functions to maintain and optimize your Znuny instance. Furthermore, AI integration opens up possibilities for leveraging artificial intelligence for tasks such as automatic ticket categorization and text analysis, boosting efficiency. For broader enhancements, Znuny add-ons are available as plugins and extensions on platforms like OpenITSMHub, providing ready-made solutions. Lastly, the Znuny REST API facilitates seamless integrations with other IT systems and enables extensive automation, allowing Znuny to fit perfectly into your existing IT landscape.
Quellen:
What is Znuny's relationship to OTRS?
Znuny is a direct continuation and fork of the OTRS Project, which was originally created by Martin Edenhofer in 2001. Specifically, Znuny emerged after OTRS AG discontinued the maintenance of the ((OTRS)) Community Edition in 2020. Recognizing the need for continued support for the widely used open-source version, the Znuny project was established to provide ongoing bugfixes and security updates for former users of OTRS Community Edition (6.0.x) for a long-term period (LTS). This means Znuny has inherited the robust foundation of OTRS and has evolved independently, offering its own set of features and improvements while ensuring a stable and secure platform for service management.
Quellen: