The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.

Source string Source string

English Actions
Include tickets of subqueues per default when selecting a queue.
Include unknown customers in ticket filter.
Includes article create times in the ticket search of the agent interface.
Incoming Phone Call.
IndexAccelerator: to choose your backend TicketViewAccelerator module. "RuntimeDB" generates each queue view on the fly from ticket table (no performance problems up to approx. 60.000 tickets in total and 6.000 open tickets in the system). "StaticDB" is the most powerful module, it uses an extra ticket-index table that works like a view (recommended if more than 80.000 and 6.000 open tickets are stored in the system). Use the command "bin/otrs.Console.pl Maint::Ticket::QueueIndexRebuild" for initial index creation.
Indicates if a bounce e-mail should always be treated as normal follow-up.
Indonesian
Inline
Input
Interface language
Internal communication channel.
International Workers' Day
It is possible to configure different skins, for example to distinguish between diferent agents, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex.
It is possible to configure different skins, for example to distinguish between diferent customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex.
It is possible to configure different themes, for example to distinguish between agents and customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid theme on your system. Please see the example entries for the proper form of the regex.
It was not possible to check the PGP signature, this may be caused by a missing public key or an unsupported algorithm.
Italian
Italian stop words for fulltext index. These words will be removed from the search index.
Ivory
Ivory (Slim)
Japanese
JavaScript function for the search frontend.
Korean
Language
Large
Last Screen Overview
Last customer subject
Lastname Firstname
Lastname Firstname (UserLogin)
Lastname, Firstname
Lastname, Firstname (UserLogin)

Loading…

User avatar None

New source string

OTRS / i18nEnglish

New source string 4 years ago
Browse all component changes

Things to check

Long untranslated

The string has not been translated for a long time

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
SysConfig
Flags
read-only
String age
4 years ago
Source string age
4 years ago
Translation file
string 5081