Table of Contents
The following system configuration settings are available to OTRS administrators by accessing the Admin page of the OTRS web interface - adding agents, customers and queues, ticket and mail settings, installing additional packages such as FAQ and ITSM, and much more.
Agents who are members of the admin group can access the Admin area by clicking the Admin link in the navigation bar (see figure below). Agents without sufficiently elevated access rights will not be able to access this link.
By clicking the link Agents, you get access to the agent management screen of OTRS (see figure below). Administrators can add, change or deactivate agent accounts. Furthermore they can also manage agent preferences, including the language and notification settings for the individual agent's interface.
An OTRS agent account may be deactivated but not deleted. Deactivation is done by setting the Valid flag to invalid or invalid-temporarily.
To register an agent, click on the "Add agent" button, enter the required data and press the Submit button at the bottom of the screen, as shown in Figure.
After the new agent account has been created, you should make the agent a member of one or more groups or roles. Information about groups and roles is available in the Groups and Roles sections of this chapter.
Every agent's account should belong to at least one group or role. In a brand new installation, there are three pre-defined groups available, as shown in Table 4-1.
Table 4.1. Default groups available on a fresh OTRS installation
|admin||Allowed to perform administrative tasks in the system.|
|stats||Qualified to access the stats module of OTRS and generate statistics.|
|users||Agents should belong to this group, with read and write permissions. They can then access all functions of the ticket system.|
In a brand new OTRS installation, the agent 'root@localhost' belongs by default to the admin, stats and users groups.
You can access the group management page (see figure below) by clicking the Groups link in the admin area.
As with agents, an OTRS group may be deactivated but not deleted. Deactivation is done by setting the Valid flag to invalid or invalid-temporarily.
To add an agent to a group, or to change the agents who belong to a group, you can use the link Agents <-> Groups from the Admin page (see figure below).
An overview of all groups and agents in the system is displayed on this page. You can also use the available filters to find a specific entity. If you want to change the groups that an agent is a member of, just click on the agent's name (see figure below). To change the agents associated with a group, just click on the group you want to edit (see figure below).
Each group has a set of rights associated with it, and each group member (agent) may have some combination of these rights for themselves. A list of the permissions / rights is shown in Table 4-2.
Table 4.2. Rights associated with OTRS groups
|chat_observer||Agents may take part silently in a chat (available in OTRS Business Solution™).|
|chat_participant||Agents may normally participate in a chat (available in OTRS Business Solution™).|
|chat_owner||Agents have full rights for a chat and can accept chat requests (available in OTRS Business Solution™).|
|ro||Read only access to the tickets, entries and queues of this group.|
|move into||Right to move tickets or entries between queues or areas that belong to this group.|
|create||Right to create tickets or entries in the queues or areas of this group.|
|note||Right to add notes to tickets or entries in the queues or areas of this group.|
|owner||Right to update the owner of tickets or entries in queues or areas that belong to this group.|
|priority||Right to change the priority of tickets or entries in queues or areas that belong to this group.|
|rw||Full read and write access on tickets or entries in the queues or areas that belong to this group.|
By default, the QueueView only lists tickets in queues that an agent has rw access to, i.e., the tickets the agent needs to work on. If you want to change this behaviour, you can set Ticket::Frontend::AgentTicketQueue###ViewAllPossibleTickets to Yes.
Not all available permissions are shown by default. These additional permissions can be added.
Table 4.3. Additional permission groups
|stats||Gives access to the stats page.|
|bounce||The right to bounce an email message (with bounce button in ticketZoom).|
|compose||The right to compose an answer for a ticket.|
|customer||The right to change the customer of a ticket.|
|forward||The right to forward a messages (with the forward button).|
|pending||The right to set a ticket to pending.|
|phone||The right to add a phonecall to a ticket.|
|responsible||The right to change the responsible agent for a ticket.|
These permissions can be added by changing the System::Permission
Roles are a powerful feature to manage the access rights of many agents in a very simple and quick manner. They are particularly useful for large, complex support systems with a lot of agents, groups and queues. An example below explains when they should be used.
Suppose that you have a system with 100 agents, 90 of them with access to a single queue called "support" where all support requests are handled. The "support" queue contains multiple sub queues. The other 10 agents have permission to access all queues of the system. These 10 agents dispatch tickets, watch the raw queue and move spam messages into the "junk" queue.
The company now opens a new department that sells some products. Order request and acceptance, order confirmation, bills, etc. must be processed, and some of the company's agents are supposed to do this using OTRS. The different agents have to get access to the new queues that must be created.
Because it would take a long time to change the access rights for the individual agents manually, roles that define the different access levels can be created. The agents can then be added to one or more roles, with their access rights being modified automatically. If a new agent account is created, it is also possible to add this account to one or more roles.
Roles are really useful when dealing with complex organizations and when maintaining larger OTRS installations. Proper care is advised though. Mixing Agent to Group with Agent to Role mappings can make for a complex access control scheme, that is difficult to understand and maintain. If you wish to use only roles and disable the Agents <-> Groups option in the Admin area, you can do so by modifying the Frontend::Module###AdminUserGroup in the SysConfig. Be aware that this won't remove already existing Agents to Group assignments!
You can access the role management section (see figure below) by clicking the Roles link on the Admin page.
As with agent and groups, roles once created can be deactivated but not deleted. To deactivate, set the Valid option to invalid or invalid-temporarily.
An overview of all roles in the system is displayed. To edit a role's settings, click on the role's name. In a fresh new OTRS installation, there are no roles defined by default. To register one, click on the "Add role" button, provide the needed data and submit it (see figure below).
To get an overview of all roles and agents in the system, click on the link Roles <-> Agents on the Admin page. You can also use filters to find a specific element. If you want to change the roles associated with an agent, just click on the agent's name (see figure below). To change the agents associated with a role, click on the role you want to edit (see figure below).
To get an overview of all roles and groups in the system, click on the link Roles <-> Groups on the Admin page. You will see a similar screen as the one shown in the Figure. You can also use filters to find a specific entity.
To define the different access rights for a role, click on the name of a role or a group (see below the Figures 4.13 and 4.14, respectively).
OTRS supports different types of users. Using the link "Customers" (via the navigation bar, or the Admin page), you can manage the accounts of your customers (see figure below), who can log into the system via the Customers interface (customer.pl). Through this interface, your customers can not only create tickets but also review their past tickets for new updates. It is important to know that a customer is needed for the ticket history in the system.
You can search for a registered customer, or edit their settings by clicking on their name. You also have the possibility to change the customer back-end, for further information please refer to the chapter about external back-ends.
To create a new customer account, click on the "Add customer" button (see figure below). Some of the fields are mandatory, i.e., they have to contain values, so if you leave one of those empty, it will be highlighted in red.
Customers can access the system by providing their username and password. The CustomerID is needed by the system to identify the user and associated tickets. Since the email address is a unique value, it can be used as the ID.
As with agents, groups and roles, customers can not be deleted from the system, only deactivated by setting the Valid option to invalid or invalid-temporarily.
Customer users can also be added to a group, which can be useful if you want to add customers of the same company with access to one or a few queues. First create the group to which your customers will belong, via the Group management module. Then add the queues and select the new group for the queues.
The next step is to activate the customer group support. This can be done with the configuration parameter CustomerGroupSupport, from the Admin SysConfig option. Using the parameter CustomerGroupAlwaysGroups, you can specify the default groups for a newly added customer, so that every new account will be automatically added to these groups.
Through the link "Customers <-> Groups" you can manage which customer shall belong to the different groups (see figure below).
To define the different groups a customer should be part of and vice versa, click on the corresponding customer username or group (see below the Figures 4.18 and 4.19, respectively).
Clicking on the link "Queues" of the Admin page, you can manage the queues of your system (see figure below). In a new OTRS installation there are 4 default queues: Raw, Junk, Misc and Postmaster. All incoming messages will be stored in the "Raw" queue if no filter rules are defined. The "Junk" queue can be used to store spam messages.
Here you can add queues (see figure below) and modify them. You can specify the group that should use the queue. You can also set the queue as a sub-queue of an existing queue.
You can define an unlock timeout for a queue - if an agent locks a ticket and does not close it before the unlock timeout has passed, the ticket will be automatically unlocked and made available for other agents to work on.
There are three escalation time settings that can be associated at queue level:
Escalation - First Response Time
After creation of the ticket, if the time defined here expires without any communication with the customer, either by email or phone, the ticket is escalated.
Escalation - Update Time
If there is a customer followup either via e-mail or the customer portal, that is recorded in the ticket, the escalation update time is reset. If there is no customer contact before the time defined here expires, the ticket is escalated.
Escalation - Solution Time
If the ticket is not closed before the time defined here expires, the ticket is escalated.
With 'Ticket lock after a follow-up', you can define if a ticket should be set to 'locked' to the old owner if a ticket that has been closed and later is re-opened. This ensures that a follow up for a ticket is processed by the agent that has previously handled that ticket.
The parameter for the system address specifies the email address that will be used for the outgoing tickets of this queue. There is also the possibility to associate a queue with a salutation and a signature, for the email answers. For more detailed information, please refer to the sections email addresses, salutations and signatures.
As with agents, groups and customers, queues cannot be deleted, only deactivated, by setting the Valid option to invalid or invalid-temporarily.
A salutation is a text module for a template. Salutations can be linked to one or more queues, as described in the section about queues. A salutation is used only if a ticket from a queue the salutation is linked to, is answered. To manage the different salutations of your system, use the "Salutations" link of the admin area (see figure below).
After a default installation there is already one salutation available, "system standard salutation (en)".
To create a new salutation, press the button "Add salutation", provide the required data and submit it (see figure below).
It is possible to use variables in salutations. When you respond to a ticket, the variable names will be replaced by their values.
The different variables you can use in templates are listed in the lower part of the salutation screen. If you use, for example, the variable <OTRS_LAST_NAME> the last name of the ticket's sender will be included in your reply.
As with other OTRS entities, salutations cannot be deleted, only deactivated by setting the Valid option to invalid or invalid-temporarily.
Another text module for a template is the signature. Signatures can be linked to a queue, as described in the section about the queues. Please note that a signature will only be appended to a template text, if it has previously been linked to a queue. You can manage the signatures in your system by accessing the "Signatures" link of the Admin page, (see figure below).
After a fresh installation of OTRS, there is one predefined signature stored in your system, "system standard signature (en)".
To create a new signature, press the button "Add signature", provide the needed data and submit it (see figure below).
Like salutations, signatures can also contain dynamic content, such as the first and last name of the agent who answers the ticket. Here too, variables can be used to replace the content of the signature text for every ticket. See the lower part of the signatures screen for the variables which can be used. If you include the variable <OTRS_LAST_NAME> in a signature for example, the last name of the agent who answers the ticket will replace the variable.
As with salutations, signatures too cannot be deleted, only deactivated by setting the Valid option to invalid or invalid-temporarily.
You can also optionally add one or more attachments to a template. If the template is selected, the attachments will be attached to the message composition window. If necessary, the agent can remove the attachment from an individual template before sending it to the customer.
Through the "Attachment" link of the Admin page, you can load the attachments into the database of the system (see figure below).
To create a new attachment, press the button "Add attachment", provide the required data and submit it (see figure below).
If an attachment is stored it can be linked to one or more templates. Click on the "Attachment <-> Templates" link of the Admin page (see figure below).
To associate different attachments with a specific template and vice versa, click on the corresponding template name or attachment (see below the Figures 4.29 and 4.30, respectively).
To speed up ticket processing and to standardize the look of answers, you can define templates in OTRS. A template can be linked to one or more queues and vice versa.
There are different kind of templates that are used in different parts of OTRS and they have its own purpose, the following is the list of possible template types:
Answer: To be used as a ticket response or reply
Create: To be used in New Phone or Email ticket
Forward: To be used to forward an article to someone else
PhoneCall: To be used in the Phone Call Inbound and Outbound screens
Answer templates can be accessed in two ways, from the ticket zoom screen in the article menu, or on a quicker way: from any ticket overview large screen such as Status View or Ticket View. For a fresh OTRS installation, the "empty answer" template (Answer) is set as the default for every queue.
As soon as Forward templates are added and assigned to queues, the "Forward" button in ticket zoom (that normally leads to a empty text forward screen) will change into a selection control, the selection is filled with the added Forward templates, by choosing one of the templates, the forward screen will be shown prefilled with the template text and attachments (similar to the reply selection box with the Answer templates).
Creating templates of type Create and PhoneCall will make visible the "Text Template" selection box in their respective screens, choosing a template for the list will populate the "Text" and "Attachment" fields (if available in the template). Notice that any previous change in the Text or attachments will be overwritten by selecting a template.
Clicking the "Templates" link on the Admin page brings you to the Template management screen (see figure below).
To create a new template, click on the "Add template" button, provide the required data (make sure to select the appropriate template type) and submit it (see figure below).
To add/remove templates to one or more queues, click on the "Templates <-> Queues" link on the Admin page (see figure below). You can also use filters to get information regarding a specific entity.
To define the different templates that will be available for a queue and vice versa, click on the corresponding template or queue (see below the Figures 5.32 and 5.33, respectively).
When choosing a template, additional information could be added to the template text, this depends on the template type:
PhoneCall and Create templates does not add any content to the template text, however New Email Ticket screen adds the queue assigned signature to the resulting email body (this screen has a separated box to visualize the signature).
Answer templates text when selected also included the salutation associated with the queue, then the text of the template, then the quoted ticket text, and finally the signature associated with the queue.
Forward templates are similar to Answer templates, but they does not include the salutation part.
OTRS allows you to send automatic responses to customers based on the occurrence of certain events, such as the creation of a ticket in a specific queue, the receipt of a follow-up message in regards to a ticket, the closure or rejection of a ticket, etc. To manage such responses, click the link "Auto responses" on the Admin page (see figure below).
To create an automatic response, click on the button "Add auto response", provide the needed data and submit it (see figure below).
The subject and text of auto responses can be generated by variables, just as in signatures and salutations. If you insert, for example, the variable <OTRS_CUSTOMER_EMAIL> into the body of the auto answer, the first 5 lines of the customer mail text will be inserted into the auto answer. You will find more details about the valid variables that can be used at the bottom of the screen shown in the Figure.
For every automatic answer, you can specify the event that should trigger it. The system events that are available after a default installation are described in the Table 4-4.
Table 4.4. Events for auto responses
|auto reply||Creation of a ticket in a certain queue.|
|auto reply/new ticket||Reopening of an already closed ticket, e.g. if a customer replies to such ticket.|
|auto follow up||Reception of a follow-up for a ticket.|
|auto reject||Automatic rejection of a ticket, done by the system.|
|auto remove||Deletion of a ticket, done by the system.|
As with other OTRS entities, auto responses too cannot be deleted, only deactivated, by setting the Valid option to invalid or invalid-temporarily.
To add an auto response to a queue, use the "Auto Response <-> Queues" link on the Admin page (see figure below). All system events are listed for every queue, and an auto answer with the same event can be selected or removed via a listbox.
To define the different auto responses that will be available for a queue, click on the corresponding queue name (see figure below). It is also possible to edit an existing auto response - to do so, click on the response and edit in the same manner as editing a new auto response.
To enable OTRS to send emails, you need a valid email address to be used by the system. OTRS is capable of working with multiple email addresses, since many support installations need to use more than one. A queue can be linked to many email addresses, and vice versa. The address used for outgoing messages from a queue can be set when the queue is created. Use the "Email Addresses" link from the Admin page to manage all email addresses of the system (see figure below).
If you create a new mail address (see figure below),you can select the queue or sub queue to be linked with it. This link enables the system to sort incoming messages via the address in the To: field of the mail into the right queue.
As with other OTRS entities, email addresses cannot be deleted, only deactivated by setting the Valid option to invalid or invalid-temporarily.
OTRS allows ticket notifications to be sent to agents and customers, based on the occurrence of certain events. Agents can customize their ticket notification settings via the preferences link.
Through the "Ticket Notifications" link on the Admin page, you can manage the ticket notifications of your system (see figure below). OTRS comes with a set of predefined notifications that cover a wide range of use cases.
You can customize many aspects of the notifications. Click on the notification you want to change, and its content will be loaded for editing (see figure below).
You can edit the basic data of this notification such as name and comment, and control if the agents may choose to receive this notification (per transport method). For every language, a subject and body can be added/edited to configure what will actually be sent as the notification content.
Just as with signatures and salutations, it is possible to dynamically create the content of a notification by using special variables. You can find a list of variables at the bottom of the screen.
You can choose which events should trigger this notification, and limit it to tickets which match certain criteria (ticket and/or article filter). This makes it possible to create different notifications for different queues, priorities or other criteria that might be relevant for your system.
The recipients of the notification can be configured according to different criteria (groups, roles, individual agents etc.). All configured recipients will receive the notification.
Additionally, you can specify if the notification should be sent to agents who are out of office, and limit the sending to once per day and ticket (e. g. pending reminder notification).
Notifications can be sent with different notification methods. The "Email" notification method is available in OTRS Free, with OTRS Business Solution™ you also get the possibility to store and view the notifications in the database (so that no email client is needed to use OTRS) as well as to send them via SMS (e. g. for very important notifications).
The field 'Additional recipient email addresses' provides the possibility to use OTRS-tags like <OTRS_TICKET_DynamicField_...> to insert values from the current ticket. The according SMS field (only available in OTRS Business Solution™) also has this feature.
Since OTRS 5s Email transport contains security options for each notification, that includes signing and encrypting possibilities with PGP and S/MIME and the opportunity to decide what to do in case of missing key or certificate.
OTRS can process incoming S/MIME encoded messages and sign outgoing mails. Before this feature can be used, you need to activate it and change some configuration parameters in the SysConfig.
The "S/MIME Certificates" link on the Admin page allows you to manage your S/MIME certificates (see figure below). You can add or remove certificates, and also search through the SMIME data.
OTRS handles PGP keys, which allows you to encrypt/decrypt messages and to sign outgoing messages. Before this feature can be used, you need to activate it and change some configuration parameters in the SysConfig.
Through the "PGP Keys" link on the Admin page, it is possible to manage the key ring of the user who shall be used for PGP with OTRS (see figure below), e.g. the local OTRS user or the web server user. It is possible to add and remove keys and signatures, and you can search through all data in your key ring.
Through the "States" link on the Admin page, you can manage the different ticket states you want to use in the system (see figure below).
After a default setup, there are some states defined:
pending auto close+
pending auto close-
Every state is linked to a type, which needs to be specified if a new state is created. By default the state types are:
The SysConfig link leads to the section where many OTRS configuration options are maintained.
The SysConfig link on the Admin page loads the graphical interface for system configuration (see figure below). You can upload your own configuration files for the system, as well as backup all your current settings into a file. Almost all configuration parameters of the OTRS framework and installed applications can be viewed and changed through this interface. Since all configuration parameters are sorted into groups and sub groups, it is possible to navigate quickly through the vast number of existing parameters. It is also possible to perform a full-text search through all of the configuration parameters.
The graphical interface for system configuration is described in more detail in the chapter "Configuring the system through the web interface".
There are several possibilities to transport new emails into the ticket system. One way is to use a local MTA and the otrs.PostMaster.pl script that pipes the mails directly into the system. Another possibility is the use of mail accounts which can be administrated through the web interface. The "PostMaster Mail Accounts" link on the Admin page loads the management console for the mail accounts (see figure below). OTRS supports the mail protocols: POP3, POP3S, IMAP and IMAPS.
See the section about PostMaster Mail Accounts for more details.
OTRS has the capability to filter incoming email messages. For example, it is possible to put certain emails automatically into specified queues, or to set a specific state or ticket type for some mails. The filters apply to all incoming mails. You can manage your filters via the link "PostMaster Filter" on the Admin page (see figure below).
A filter consists of one or more criteria that must be met in order for the defined actions to be executed on the email. Filter criteria may be defined for the headers or the body of an email, e.g. search for specific header entries, such as a sender address, or on strings in the body. Even regular expressions can be used for extended pattern matching. If your filter matches, you can set fields using the X-OTRS headers in the GUI. These values will be applied when creating the ticket or follow-up message in OTRS. The Table 4-5 lists the different X-OTRS headers and their meaning.
You also can use X-OTRS-FollowUp-* headers to set values for follow up emails.
Table 4.5. Function of the different X-OTRS-headers
|X-OTRS-Priority:||1 very low, 2 low, 3 normal, 4 high, 5 very high||Sets the priority of a ticket.|
|X-OTRS-Queue:||Name of a queue in the system.||Sets the queue where the ticket shall be sorted. If set in X-OTRS header, all other filter rules that try to sort a ticket into a specific queue are ignored. If you use a sub-queue, specify it as "Parent::Sub".|
|X-OTRS-Lock:||lock, unlock||Sets the lock state of a ticket.|
|X-OTRS-Ignore:||Yes or True||If this X-OTRS header is set to "Yes", the incoming message will completely be ignored and never delivered to the system.|
|X-OTRS-State:||new, open, closed successful, closed unsuccessful, ...||Sets the next state of the ticket.|
|X-OTRS-State-PendingTime:||e. g. 2010-11-20 00:00:00||Sets the pending time of a ticket (you also should sent a pending state via X-OTRS-State). You can specify absolute dates like "2010-11-20 00:00:00" or relative dates, based on the arrival time of the email. Use the form "+ $Number $Unit", where $Unit can be 's' (seconds), 'm' (minutes), 'h' (hours) or 'd' (days). Only one unit can be specified. Examples of valid settings: "+50s" (pending in 50 seconds), "+30m" (30 minutes), "+12d" (12 days). Note that settings like "+1d 12h" are not possible. You can specify "+36h" instead.|
|X-OTRS-Type:||default (depends on your setup)||Sets the type of a ticket (if Ticket::Type is activated).|
|X-OTRS-Service:||(depends on your setup)||Sets the service of a ticket (if Ticket::Service is active). If you want to set a sub-service you should specify it as "Parent::Sub".|
|X-OTRS-SLA:||(depends on your setup)||Sets the SLA of a ticket (if Ticket::Service support is active).|
|X-OTRS-CustomerUser:||CustomerUser||Sets the customer user for the ticket.|
|X-OTRS-CustomerNo:||CustomerNo||Sets the customer ID for this ticket.|
|X-OTRS-SenderType:||agent, system, customer||Sets the type of the ticket sender.|
|X-OTRS-ArticleType:||email-external, email-internal, email-notification-ext, email-notification-int, phone, fax, sms, webrequest, note-internal, note-external, note-report||Sets the article type for the incoming ticket.|
|X-OTRS-DynamicField-<DynamicFieldName>:||Depends on Dynamic Field configuration (Text: Notebook, Date: 2010-11-20 00:00:00, Integer: 1)||Saves an additional info value for the ticket on <DynamicFieldName> Dynamic Field.|
|X-OTRS-Loop:||True||If this X-OTRS header is set, no auto answer is delivered to the sender of the message (mail loop protection).|
You should specify a name for every filter rule. Filter criteria can be specified in the section "Filter Condition". Choose via the listboxes for "Header 1", "Header 2" and so on for the parts of the messages where you would like to search, and specify on the right side the values you wish to filter on. In the section "Set Email Headers", you can choose the actions that are triggered if the filter rules match. You can select for "Header 1", "Header 2" and so on to select the X-OTRS-Header and set the associated values (see figure below).
Filter rules are evaluated in alphabetical order, and are all executed except if the "Stop after match" setting has been set to "Yes" in one of the rules (in this case evaluation of the remaining filters is canceled).
Example 4.1. Sort spam mails into a specific queue
A useful filter rule would be to let OTRS automatically move mails marked for spam, by using a spam detection tool such as SpamAssassin, into the "Junk" queue. SpamAssassin adds the "X-Spam-Flag" header to every checked mail. When the mail is marked as spam, the Header is set to "Yes". So the filter criteria would be "X-Spam-Flag: Yes". To create a filter rule with this criteria you can insert the name as, for example, "spam-mails". In the section for "Filter Condition", choose "X-Spam-Flag:" for "Header 1" from the listbox. Insert "Yes" as value for this header. Now the filter criteria is specified. To make sure that all spam mails are placed into the "Junk" queue, choose in the section for "Set Email Headers", the "X-OTRS-Queue:" entry for "Header 1". Specify "Junk" as value for this header. Finally add the new filter rule to activate it for new messages in the system.
There are additional modules, that can be used to filter incoming messages more specifically. These modules might be useful when dealing with larger, more complex systems.
The GenericAgent is a tool to execute tasks automatically. The GenericAgent, for example, can close or move tickets, send notifications on escalated tickets, etc.
Click the link "GenericAgent" on the Admin page (see figure below). A table with all automated jobs in the system is displayed. These jobs can then be edited, run manually or removed entirely.
Click the "Add job" button to create a new job. You first need to supply a name. Then you can specify how the job will be executed: automatic at fixed times (like a cronjob, this mode will operate on all tickets found by the ticket filter) or based on ticket events (right after a single ticket was modified, if it matches the ticket filter). Note that if you manually run event based jobs from the overview screen, they will operate on all tickets fund by the ticket filter.
For every job, you can specify a ticket filter, for example to only operate on tickets in a certain queue. All filter criteria must be met for a job to be run on a ticket.
Finally, the ticket can be modified by setting various ticket fields like a new queue or state. It is possible to attach a note to the ticket(s) or run a customized module. You also have the option to delete the ticket(s) from the database. This can be useful to purge outdated or invalid data from the system.
If you use the ticket delete function, all affected tickets and their attachments will be removed from the database and cannot be restored!
After editing a job, OTRS will return to the overview screen. There you have the possibility to run any job manually. If you choose to run a job, you will first see all tickets which will be affected when the job actually is run. This list helps you to verify that the job is working as intended. At this point no changes have been made to these tickets yet. Only if you confirm the screen the job will be executed.
OTRS administrators can send messages to specific users or groups. The "Admin Notification" link on the Admin page opens the screen where the agents and groups that should be notified can be selected (see figure below).
It is possible to specify the sender, subject and body text of the notification. You can also select the agents, groups and roles who should receive the message.
You can see all logged in users and their session details by clicking the "Session Management" link in the admin area (see figure below).
Some statistics about all active sessions are displayed, e.g. how many agents and customer users are logged in and the number of active sessions. Any individual session can be removed by clicking on the Kill this session link on the right-hand side of the list. You also have the option to Kill all sessions, which can be useful if you want to take the system offline. Detailed information for every session is available, too (see figure below).
System Maintenance give the option to schedule one or more maintenance periods for the system. During this period no agents or customers can login into the system (except for Agents in the "admin" group). Current logged users and customers receive a notification about the maintenance (before and during the maintenance period). Administrators have the option to kill the sessions for logged agents and customers, all this in preparation to be able to make changes in the system (e.g. a system update) in a "safe" environment.
The Start Date and the Stop Date are required fields, and the only rule for this combination is that Start Date can not be a date after the Stop Date.
After a new maintenance period is defined an overview and details about the current active sessions is shown, from there administrators can kill this sessions one by one or all of them (except current) if it is needed.
The "System Log" link on the Admin page shows the log entries of the system, reverse chronologically sorted with most recent first (see figure below).
Each line in the log contains a time stamp, the log priority, the system component and the log entry itself.
System logs are available via the web interface only on Linux / Unix systems.
The "SQL Box" link on the Admin page opens a screen that lets you query the content of the tables in the OTRS database (see figure below). It is not possible to change the content of the tables, only 'select' queries are allowed.
Using the "Package Manager" link on the Admin page, you can install and manage packages that extend the functionality of OTRS (see figure below). See the Additional applications section for a discussion on the extensions that are available from the OTRS repositories.
The Package Manager shows the OTRS addon packages you currently have installed on your server, together with their version numbers.
You can install packages from a remote host by selecting the repository in the Online Repository section, and clicking the Update repository information button. The available packages are displayed in the corresponding table. The right side of the screen shows the available packages. To install a package, click on Install. After installation, the package is displayed in the Local Repository section.
To upgrade an installed package, the list of available packages in the online repository will show Upgrade in the Action column for any package that has a higher version than the one that is installed locally. Just click Upgrade and it will install the new package version on your system.
In some cases, such as when your OTRS system is not connected to the Internet, you can also install those packages that you have downloaded to a local disk. Click the Browse button on the Actions side bar, and select the .opm file of the package on your disk. Click Open and then Install Package. After the installation has been completed, the package is displayed in the Local Repository section. You can use the same steps for updating a package that is already installed.
In special cases, you might want to configure the Package Manager, e.g., to use a proxy or to use a local repository. Just take a look at the available options in SysConfig under Framework:Core::Package.
The Web Services link leads to the graphical interface where web services (for the OTRS Generic Interface) are created and maintained (see figure below).
The graphical interface for web services configuration is described in more detail in the section "Web Service Graphical Interface".
Dynamic Fields is the place where you setup and manage custom fields for tickets and articles (see figure below).
The dynamic fields configuration is described in more detail in the section "Dynamic Fields Configuration".
Each dynamic field type has its own configuration settings and therefore its own configuration screen.
In the OTRS framework, dynamic fields can only be linked to tickets and articles by default, but they can be extended to other objects as well.