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.
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 basic component is the OTRS framework which contains all central functions for the application and the ticket system. Through the web interface of the OTRS framework, it is possible to install additional applications such as ITSM modules, integrations with Network Monitoring solutions, a knowledge base (FAQ), et cetera.
OTRS has many features. The following list gives an overview of the features included in the central framework.
The features of OTRS
Easy and initial handling with any modern web browser, even with mobile phones or other mobile computers.
A web interface to administer the system via the web is available.
A web interface to handle customer requests by employees/agents via the web is integrated.
A web interface for customers is available to write new tickets, check the state and answer existing tickets and search through their own tickets.
The web interface can be customized with different themes; own themes can be integrated.
Support for many languages.
The appearance of output templates can be customized (dtl).
Mails from and into the system can contain multiple attachments.
Support for mail attachments (MIME support).
Automatic conversion of HTML into plain text messages (increased security for sensitive content and enables faster searching).
Mail can be filtered with the X-OTRS headers of the system or via mail addresses, e.g. for spam messages.
PGP support, creation and import of own keys, signing and encrypting outgoing mail, signed and encrypted messages can be displayed.
Support for viewing and encrypting S/MIME messages, handling of S/MIME certificates.
Auto answers for customers, configurable for every queue.
Email notifications for agents about new tickets, follow-ups or unlocked tickets.
Follow-ups by references or In-Reply-To header entries.
Expanded queue view, fast overview of new requests in a queue.
Tickets can be locked.
Creation of own auto response templates.
Creation of own auto responders, configurable for every queue.
Ticket history, overview of all events for a ticket (changes of ticket states, replies, notes, etc.).
Print view for tickets.
Adding own (internal or external) notes to a ticket (text and attachments).
Access control lists for tickets can be defined.
Forwarding or bouncing tickets to other mail addresses.
Transferring tickets between queues.
Setting or changing the priority of a ticket.
The working time for every ticket can be counted.
Up-coming tasks for a ticket can be defined (pending features).
Bulk actions on tickets are possible.
Automatic and timed actions on tickets are possible with the "GenericAgent".
Full text search on all tickets is possible.
OTRS runs on many operating systems (Linux, Solaris, AIX, FreeBSD, OpenBSD, Mac OS 10.x, Microsoft Windows).
ASP support (active service providing).
Linking several objects is possible, e.g. tickets and FAQ entries.
Integration of external back-ends for the customer data, e.g. via AD, eDirectory or OpenLDAP.
Setting up an own ticket identifier, e.g. Call#, Ticket# or Request#.
The integration of your own ticket counter is possible.
Support of several database systems for the central OTRS back-end, e.g. MySQL, PostgreSQL, Oracle, MSSQL).
Framework to create stats.
utf-8 support for the front- and back-end.
Authentication for customers via database, LDAP, HTTPAuth or Radius.
Support of user accounts, user groups, and roles.
Support of different access levels for several systems components or queues.
Integration of standard answer texts.
Support of sub queues.
Different salutations and signatures can be defined for every queue.
Email notifications for admins.
Information on updates via mail or the web interface.
Escalation for tickets.
Support for different time zones.
Simple integration of own add-ons or applications with the OTRS API.
Simple creation of own front-ends, e.g. for X11, console.
The new "Customer Information Center" provides a great dashboard-like view on a customer (company). You can see
Escalated, reminder, new, and open tickets of the customer company.
Customer users (contacts) belonging to this customer company, with their individual ticket count and shortcuts for creating new tickets for them.
An overall ticket status view of the customer company.
New "switch to customer" feature makes it possible for an agent with the required permissions to look into the customers's panel with their rights.
The new process management makes it possible to represent processes within OTRS.
The customer web interface now fully supports AJAX and ACLs.
In the Customer Interface, you can now set the default ticket type for new tickets. Additionally, you can now also hide the ticket type and use a default value for all tickets created via the customer interface.
Agents can now search for tickets based on escalation time.
New option to show DynamicFields by default in ticket search.
Screen usage optimizations in the ticket screens to avoid scrolling in popup windows. For each ticket screen, the size of the richtext editor can now be configured separately.
It is now possible to move tickets to another queue from within the TicketAction dialogs (TicketNote, TicketClose etc.) after activating a configuration option. This is turned off by default.
Ticket search will now directly jump to the ticket zoom screen if only one ticket is found.
New ability to hide the Article Type from TicketActionCommon-based screens which can be helpful to fit more data in the browser window.
There is a new out-of-office dashboard widget that lists all currently unavailable agent colleagues.
New CKEditor 4 makes working with rich text content (such as HTML emails) easier and more stable.
Event Based notifications can now be sent out only for specific Article Sender Types.
The Statistics engine in OTRS now understands 'Weeks' in addition to days, months and years. This grants the ability to, for instance, create a report for tickets 'created last week', or generate a report that shows tickets created per queue per week.
It is possible to place customized DTL (template) files in
Custom/Kernel/Output/HTML, so that they override the system's default DTL files just as how this already works for Perl files.
In AdminSMIME it is now possible to display human readable certificate contents.
SysConfig now supports config setting types Date and DateTime.
When tickets are archived, the information which agent read the ticket and articles can be removed, as well as the ticket subscriptions of agents. This is active by default and helps reduce the amount of data in the database on large systems with many tickets and agents.
There is also a new script to remove this data from existing archived tickets.
Archived tickets are now always shown as 'read' by the agent.
Session management is up to 10 times faster, especially with many active users.
It is now possible to limit the number of concurrent agents and/or users to avoid server capacity overload.
Significant reduction in the number of executed database statements in ticket overviews and ticket masks in agent and customer frontend.
This will reduce the load on database servers, especially on large systems. In some cases OTRS will become visibly more responsive (if the system was slowed down by the DB load or latency).
Improved performance of LDAP user synchronization.
Improved cache performance with many cache files.
GI is a flexible framework to allow web service interconnections of OTRS with third party applications.
OTRS can act in both ways - as a provider (server, requested from remote) or requester (client, requesting remotely).
Simple web service connections can be created without programming by configuring the Generic Interface.
Complex scenarios can be realized by plugging in custom OTRS extensions that add perl code to the GI infrastructure on different architectural layers.
Connectors expose parts of OTRS to Generic Interface web services.For example, a ticket connector exposes the ticket create/update function, so that they can be used in a web service regardless which network transport is used.
A scheduler daemon process supports asynchronous event handling. This is useful to asynchronously start web service requests from OTRS to another system, after the agent''s request has been answered (e.g. when a ticket has been created). Otherwise, it might block the response, resulting in increased response times for the agent.
With the Generic Interface, new web services can be configured easily by using existing OTRS modules, without additional code. They can be combined to create a new web service. When configuring a new web service connection, the administrator has to add:
A new web service in the admin GUI
The basic meta data (Transport type (SOAP), URL etc.) and
Existing operations (part of a connector) and specify for each operation how the data must be mapped (inbound and outbound)
A Generic Interface Debugger will help the OTRS administrator to check how requests are coming in and how they are handled through the different layers.
Network transports: SOAP/HTTP. Others like REST and JSON are scheduled to be added in the future depending on customers demand.
Configurable data mapping Graphical User Interface for key/value transformations with respect to incoming and outgoing data.
Graphical debugger to check the configuration and flow of information of configured web services.
A ticket connector allowing the use of OTRS as a web service for ticket handling.
Additional network transports (REST, JSON).
The GI will replace the iPhoneHandle as the backend for mobile apps.
Additional connectors will be added to provide more parts of OTRS for use with web services (e.g. to allow the creation, update, or deletion of agents, users, services or CIs).
The DynamicFields Feature replaces the existing ticket and article FreeText and FreeTime fields with a dynamic structure that will also allow to create custom forms in OTRS.
An unlimited amount of fields can be configured using an own graphical user interface for administration.
The fields can have different types that can be used for both, tickets and articles. Available by default are:
Date and time
New custom field types (e.g. custom field type dropdown with an external data source) can be added with small effort as the fields are created in a modular, pluggable way.
A future scenario is, that DynamicFields can be used for objects other than tickets or in custom modules. For example, a custom module adding objects to handle "orders" in OTRS could use the DynamicFields to attach properties/data to these orders.
A database update script will transform historic FreeText fields and related configuration settings into the new structure.
Multiple email addresses can now be specified as 'To:', 'CC:' or 'BCC:' when creating a new phone or email ticket.
Inbound phone calls can now be registered within an existing tickets (until now, only outbound calls were registered).
It is now possible to exclude articles of certain sender types (e.g. articles from internal agents) in the SysConfig from being displayed in the overview preview mode.
A certain article type can be configured which will display articles of that type as expanded by default when the view is accessed.
The screen shown after moving a ticket is now configurable. Options are the ticket zoom view (LastScreenView) or the ticket list (LastScreenOverview).
With the new bulk action, outbound emails can now be sent from multiple tickets at the same time. As tickets can have different queues, and these queues each can have different templates, salutations and signatures, these are not used in the Bulk Action email.
An additional bulk action allows configuring the ticket type for selected tickets.
OTRS will now create events for each of the available escalation types (response, update and resolution). This allows performing actions (such as notifications) before the escalation occurs, in the moment it occurs, and in the moment that the escalation ends.
A new generic agent notification module allows the OTRS administrator to define messages that will be shown in the agent web front-end when agents log into the system.
All kinds of times will now be calculated by and based on the application server only solving the issues that were caused by variances between the clock times of application and data base servers.
The speed for rendering and article display was improved, thanks to Stelios Gikas <email@example.com>!
PostgreSQL 9.1 support added.
A new legacy driver is now available for PostgreSQL 8.1 or earlier versions.
User Centered redesign of the Graphical User Interface which results in a dramatic shift from a comprehensive but static to a more powerful and dynamic application using state-of-the art technologies like Ajax, xHTML and optimized CSS.
New Ticket and Article Indicator
This new feature has been implemented on both ticket and article level. At a glance, an agent is now able to check for any updates within a ticket or on the article level to check for new and unread articles. You benefit from increased transparency and decreased response times.
Optimized Fulltext Search
The new search feature allows you to flexibly customize the way you browse the information base. Options provided by the new search feature range from single search-string searches to complex multi-string boolean search operations including various operators. You benefit from fully customizable searches adjusted according to your needs.
New Ticket Zoom View
The redesign based on Ajax technology allows agents to display complex and linked information structures in real-time while keeping the agents' current working environment. The agent will benefit from increased orientation and increased workflow efficiency.
Global Ticket Overviews
Well known from OTRS 2.4, the global ticket overviews have been optimized to achieve increased inter- activity. Depending on the use case and preferences of your agents, they can easily change the ticket overviews layout according to their specific needs. Options are small, medium, and large, with each providing a different degree of information details.
The redesign includes common accessibility standards WCAG and WAI-ARIA which also allows disabled users to better interact with OTRS Help Desk. The US Rehabilitation Acts Section 508 has been fulfilled.
New Customer Interface
The customer web front-end can be integrated to your organization's intranet and is fully integrated into the redesigned help desk system.
OTRS 3.0 now offers a new archiving feature. With a separated archive, you'll benefit from a reduced time spent for searches and increased display of results.
OTRS can be installed on many different operating systems. OTRS can run on linux and on other unix derivates (e.g. OpenBSD or FreeBSD). You can also run it on Microsoft Windows. OTRS does not have excessive hardware requirements. We recommend using a machine with at least a 2 GHz Xeon or comparable CPU, 2 GB RAM, and a 160 GB hard drive for a small setup.
To run OTRS, you'll also need to use a web server and a database server. Apart from that, you should install perl and/or install some additional perl modules on the OTRS machine. The web server and Perl must be installed on the same machine as OTRS. The database back-end may be installed locally or on another host.
For the web server, we recommend using the Apache HTTP Server, because its module mod_perl greatly improves the performance of OTRS. Apart from that, OTRS should run on any web server that can execute Perl scripts.
You can deploy OTRS on different databases. You can choose between MySQL, PostgreSQL, Oracle, or Microsoft SQL Server. If you use MySQL you have the advantage that the database and some system settings can be configured during the installation, through a web front-end.
For Perl, we recommend using at least version 5.8.8. You will need some additional modules which can be installed either with the Perl shell and CPAN, or via the package manager of your operating system (rpm, yast, apt-get).
Apache2 + mod_perl2 or higher (recommended, mod_perl is really fast!)
Webserver with CGI support (CGI is not recommended)
Microsoft Internet Information Server (IIS) 6 or higher
MySQL 5.0 or higher
PostgreSQL 7.0 or higher (8.2 or higher recommended)
Oracle 10g or higher
Microsoft SQL Server 2005 or higher
The section in the manual about installation of Perl modules describes in more detail how you can set up those which are needed for OTRS.
If you install a binary package of OTRS, which was built for your operating system (rpm, Windows-Installer), either the package contains all Perl modules needed or the package manager of your system should take care of the dependencies of the Perl modules needed.
Internet Explorer 8.0 or higher (agent interface)
Internet Explorer 7.0 or higher (customer interface)
Mozilla Firefox 3.6 or higher
Opera 10 or higher
Safari 4 or higher
OTRS has a large user community. Users and developers discuss OTRS and exchange information on related issues through the mailing-lists. You can use the mailing lists to discuss installation, configuration, usage, localization and development of OTRS. You can report software bugs in our bug tracking system.
The homepage of the OTRS community is: http://www.otrs.com/open-source/.
Whether you need help in configuring or customizing OTRS or you want to be on the safe side, don't hesitate to contact us: We offer a wide range of professional services such as world-wide enterprise support, consulting and engineering including process design, implementation, customization, application support, and fully managed service.
Our Service Contracts guarantee instant help and professional support as well as support assessment and last but not least free access to OTRS Feature Add-ons - useful additional features for your OTRS.
The OTRS Group offers specific training programs in different countries. You can either participate in one of our public OTRS Administrator trainings which take place regularly, or benefit from an inhouse training that covers all the specific needs of your company.