znuny Goto Github PK

repos: 70.0 gists: 0.0

Name: Znuny GmbH - Enterprise Services

Type: Organization

Bio: Making help desk software that works for you.

Twitter: znuny

Location: Everywhere

Blog: https://www.znuny.com

Znuny

Znuny is a continuation of the ((OTRS)) Community Edition (version 6.0.30) which was declared end of life (EOL) at the end of December 2020.

The primary goal for this project is to provide a maintained and stable version of the well known ticket system and improve it with new features.

The second goal is to reestablish a connection to the community.

License

The project is distributed under the GNU General Public License (GPL v3) - see the accompanying COPYING file for general license information. If you need more details you can have a look here.

Documentation

You can find documentation here. The source code of Znuny is publicly available on GitHub.

You want to get in touch?

Software requirements

Operating system

Linux (Debian or Red Hat preferred)
Perl 5.16.0 or higher

Web server

Apache 2 + mod_perl2 or higher (recommended)
Web server with CGI support (CGI is not recommended)

Databases

MySQL 5.0 or higher
MariaDB
PostgreSQL 9.2 or higher
Oracle 10g or higher

Browsers

These browsers are NOT supported:
- Internet Explorer before version 11
- Firefox before version 31
- Safari before version 6

Vendor

This project is mainly funded by Znuny GmbH, Berlin. If you need professional support or consulting, feel free to contact us.

Znuny Website

Znuny GmbH - Enterprise Services's Projects

faq

An FAQ module to manage FAQs and also used as knowledge base.

generalcatalog

The GeneralCatalog is a reference table tool. You can add new items or update existing items in the Admin-Interface.

importexport

The Import/Export tool is a generic framework to import and export objects like tickets or config items in several formats like CSV or XML.

This package contains all other ITSM packages (GeneralCatalog, ITSMCore, ITSMIncidentProblemManagement, ITSMConfigurationManagement, ITSMChangeManagement, ITSMServiceLevelManagement, ImportExport) and makes it possible to install all of them at once.

itsm-treeviewfix

itsmchangemanagement

The Znuny::ITSM Change Management package provides change management functionalities. This package requires the ITSM Core package.

itsmconfigurationmanagement

This package implements all ITSM configuration management features. This package requires the ITSMCore package.

itsmcore

The Znuny::ITSM Core package provides basic functionality for all other ITSM packages. This package requires the GeneralCatalog package.

itsmincidentproblemmanagement

This package implements all ITSM incident management and problem management features. This package requires the ITSMCore package.

itsmservicelevelmanagement

This package implements all ITSM service level management features. This package requires the ITSMCore package.

manual

module-tools

Helper scripts for developing OTRS modules

otrs-sopm

This gem provides a class to parse, manipulate and store SOPM files and create OPM strings from them.

otrs.github.io

doc.otrs.com website content

otrsappointmentcalendar

A calendar solution for OTRS.

otrsclonedb

Helper script to migrate a Znuny database into a different RDBMS.

otrscodepolicy

OTRS code quality checker

otrshelperscripts

A collection of little helper scripts for OTRS that were created over time.

package_control_channel

Default channel file for Package Control. Follow the directions at:

sublimetextadjustments

This repository contains adjustments of the Sublime Text configuration and some OTRS snippets we at Znuny use to develop OTRS extensions and stuff.

survey

A customer survey tool to send emails to the customer after a ticket is closed. The customer can access the public interface to submit a survey with custom questions. A report of the survey can be shown in the agent interface.

systemmonitoring

This module implements a basic interface to System Monitoring Suites. It works by receiving email messages sent by the Monitoring Suite. New tickets are created in case of component failures. Once a ticket has been opened messages regarding the effected component are attached to this ticket. When the component recovers, the ticket state can be changed or the ticket can be closed.