OTRS Help Desk, ITSM

简介:

Abstract

This chapter describes the features of OTRS Help Desk (OTRS). You will find information about the hardware and software requirements for OTRS. Additionally, in this chapter you will learn how to get commercial support for OTRS, should you require it, and how to contact the community.

Basics

OTRS Help Desk (OTRS) is a web application that is installed on a web server and can be used with a web browser.

OTRS is separated into several components. The main component is the OTRS framework which contains all central functions for the application and the ticket system. It is possible to install additional applications such as OTRS::ITSM modules, integrations with Network Monitoring solutions, a knowledge base (FAQ), et cetera.

Features

OTRS has many features. The following list gives an overview of the main features included in the OTRS framework.

User interface

  • OTRS comes with separate, modern web interfaces for agents and customers.

  • It can be used on any modern web browser, including mobile plaforms and is retina ready.

  • The web interface can be customized with own themes and skins.

  • Powerful and customizable agent dashboard with personal ticket overviews and graphical statistics support.

  • An extensible reporting engine provides various statistics and report scheduling options.

  • With the ProcessManagement it is possible to define own ticket-based screens and processes (ticket workflows).

  • OTRS has a built-in rights management that can be extended with fine-grained access control lists (ACLs).

  • Support for more than 30 languages and different time zones.

Mail interface

  • Support for MIME emails with attachments.

  • Automatic conversion of HTML into plain text messages (increased security for sensitive content and enables faster searching).

  • Incoming mail can be filtered and pre-processed with complex rules, e.g. for spam messages or Queue distribution.

  • Support for PGP and S/MIME standards for key/certificate management and email processing.

  • Automatic responses, configurable for every queue.

  • Email notifications for agents about new tickets, follow-ups or unlocked tickets.

  • It is possible to define an own Ticket identifier to recognize follow-ups, e.g. Call#, Ticket# or Request#. There are different ticket number generators (date-based, random etc.) and you can integrate your own as well. Follow-ups can also be recognized by In-Reference-To headers or external ticket numbers.

Tickets

  • OTRS uses Tickets to gather all external an internal communication that belongs together. These tickets are organized in Queues.

  • There are many different ways of looking at the tickets in a system (based on Queues, Status, Escalation etc.) in different level of detail (small/medium/preview).

  • The Ticket history records all changes to a ticket.

  • Tickets can be changed in many ways, such as replying, forwarding, bouncing, moving to another Queue, updating attributes (state, priority etc.), locking and accounting working time. It is possible to modify many tickets at once (bulk action).

  • Pending time and escalation time / SLA management allow time-based scheduling and restrictions on tickets.

  • Tickets can be linked to other tickets or other objects such as FAQ entries.

  • Automatic and timed actions on tickets are possible with the "GenericAgent".

  • OTRS comes with a powerful search engine that allows complex and fulltext searches on tickets.

System

  • OTRS runs on many operating systems (Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x, Microsoft Windows) and supports several database systems for the central OTRS back-end (MySQL, PostgreSQL, Oracle, MSSQL).

  • The core system can be extended by installing OTRS packages. There are many free packages (such as FAQ, OTRS::ITSM and others) as well as FeatureAddon packages that are available for service contract customers of the OTRS group.

  • Integration of external back-ends for the customer data, e.g. via AD, eDirectory or OpenLDAP. Customers can authenticate via database, LDAP, HTTPAuth or Radius.

  • With the GenericInterface it is easy to connect OTRS to other web services. Simple web services can be integrated without programming, complex scenarios with custom extensions. The OTRS Ticket connector allows the creation, updating and searching of tickets, via web services from a third party application.


[参考]
目录
相关文章
|
存储 域名解析 NoSQL
『MongoDB』MongoDB高可用部署架构——分片集群篇(Sharding)
📣读完这篇文章里你能收获到 - 为什么要使用分片 - Mongodb分片集群有哪些特点 - Mongodb分片集群的完整架构 - Mongodb分片集群数据分布方式 - Mongodb分片集群的设计思路 - Mongodb分片集群搭建及扩容 - 这篇文章强烈建议收藏!!!免得下次找不到
4463 2
『MongoDB』MongoDB高可用部署架构——分片集群篇(Sharding)
|
关系型数据库 MySQL Docker
docker 安装 mysql(arm64)
docker 安装 mysql(arm64)
1628 0
|
数据挖掘 Shell 测试技术
怎么用Python解析HTML轻松搞定网页数据
**Python解析HTML摘要** 本文介绍了使用Python处理HTML的常见需求,如数据提取、网络爬虫和分析,并讨论了三种解析方法。正则表达式适用于简单匹配,但对复杂HTML不理想;BeautifulSoup提供简单API,适合多数情况;lxml结合XPath,适合处理大型复杂文档。示例展示了如何用这些方法提取链接。
594 2
|
Linux 数据安全/隐私保护 网络虚拟化
centos7部署Pritunl
centos7部署Pritunl
|
缓存 Docker 容器
在Docker中,docker add copy有什么区别?
在Docker中,docker add copy有什么区别?
|
Linux
Centos7.4升级7.9失败,救援:/boot目录下文件丢失error: file ‘/initramfs-3.10.0-957.el7.x86_64.img‘ not found
以上步骤应该可以帮助你解决问题。如果问题仍然存在,可能需要更深入的排查。
428 1
|
缓存 安全 算法
Elasticsearch参数配置汇总
Elasticsearch参数配置汇总
584 0
|
关系型数据库 Linux 网络安全
开源IDC数据中心资产管理系统RackTables部署篇(一)
开源IDC数据中心资产管理系统RackTables部署篇(一)
1219 0
|
关系型数据库 MySQL
MySQL 5.7 基于 GTID 主从复制 + 并行复制 + 半同步复制
MySQL 5.7 基于 GTID 主从复制 + 并行复制 + 半同步复制
734 0

热门文章

最新文章