en	Check the official %sdocumentation%s.
ja	公式の %s ドキュメント %s をご確認ください。

en	These are the possible methods that can be used to send this notification to each of the recipients. Please select at least one method below.
ja	この通知を各受信者に送信するために使用可能な手段があります。以下より少なくとも1つ以上選択してください。

en	Filter for Communications

en	You can change the sort and order of the columns by clicking on the column header.

en	If you click on the different entries, you will get redirected to a detailed screen about the message.

en	Show only entries with specific priority and higher:

en	Filter for groups

en	Manage Customer User-Service Relations

en	Would you like to benefit from additional dynamic field types for businesses? Upgrade to %s to get access to the following field types:

en	This feature allows to add (multiple) contacts with data to tickets.

en	Is not possible to invalidate this entry, all config settings have to be changed beforehand.

en	Activate this feature to define a fixed range of years (in the future and in the past) to be displayed on the year part of the field.

en	Here you can specify an optional HTTP link for the field value in Overviews and Zoom screens.

en	If special characters (&, @, :, /, etc.) should not be encoded, use 'url' instead of 'uri' filter.

en	If filled in, this URL will be used for a preview which is shown when this link is hovered in ticket zoom. Please note that for this to work, the regular URL field above needs to be filled in, too.

en	Generic Agent Job Management

en	Edit Job

en	Add Job

en	Run Job

en	Filter for Jobs

en	Filter for jobs

en	Automatic execution values are in the system timezone.

en	Additionally or alternatively to a periodic execution, you can define ticket events that will trigger this job.

en	If a ticket event is fired, the ticket filter will be applied to check if the ticket matches. Only then the job is run on that ticket.

en	Add dynamic field

en	Last close times
ja	最終変更時間

en	No last close time settings.
ja	クローズ時間を指定しない

en	Ticket last close
ja	チケットをクローズしたのが

en	Ticket last close between
ja	チケットをクローズしたのがこの期間内

en	Do you really want to delete this error handling module?

en	The name can be used to distinguish different error handling configurations.

en	This OTRS error handling backend module will be called internally to process the error handling mechanism.

en	Configure filters to control error handling module execution.

en	Only requests matching all configured filters (if any) will trigger module execution.

en	Note: Operation is undetermined for errors occuring while receiving incoming request data. Filters involving this error stage should not use operation filter.

en	Enter a regular expression to restrict which error messages should cause error handling module execution.

en	Error message subject and data (as seen in the debugger error entry) will considered for a match.

en	Example: Enter '^.*401 Unauthorized.*\\$' to handle only authentication related errors.

en	Only execute error handling module on errors that occur during specific processing stages.

en	Example: Handle only errors where mapping for outgoing data could not be applied.

en	This identifier will be available in XSLT-Mapping and shown in debugger output.

en	Define if processing should be stopped after module was executed, skipping all remaining modules or only those of the same backend.

en	Default behavior is to resume, processing the next module.

en	Default behavior of GenericInterface web services is to send each request exactly once and not to reschedule after errors.

en	If more than one module capable of scheduling a retry is executed for an individual request, the module executed last is authoritative and determines if a retry is scheduled.

en	Retry options are applied when requests cause error handling module execution (based on processing options).

en	If a request returns an error even after a first retry, define if subsequent retries are triggered using the same interval or in increasing intervals.

en	Note: Maximum retry count might not be reached if a maximum retry period is configured as well and reached earlier.

en	This field must be empty or contain a positive number.

en	Maximum period of time for retries of failing requests before they are discarded (based on the error handling module execution time for the initial request).

en	Retries that would normally be triggered after maximum period is elapsed (according to retry interval calculation) will automatically be triggered at maximum period exactly.

en	Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum retry period at '30 minutes', retries would be triggered at 10:01, 10:03, 10:07, 10:15 and finally at 10:31=>10:30.

en	Note: Maximum retry period might not be reached if a maximum retry count is configured as well and reached earlier.

en	GenericInterface Invoker Event Settings for Web Service %s

en	And can't be repeated on the same condition.

en	Here you can add or modify your XSLT mapping code.

en	The editing field allows you to use different functions like automatic formatting, window resize as well as tag- and bracket-completion.

en	Data includes

en	Select one or more sets of data that were created at earlier request/response stages to be included in mappable data.

en	These sets will appear in the data structure at '/DataInclude/<DataSetName>' (see debugger output of actual requests for details).

en	Data key regex filters (before mapping)

en	Data key regex filters (after mapping)

en	The data structure will be traversed recursively and all configured regexes will be applied to all keys.

en	Use cases are e.g. removing key prefixes that are undesired or correcting keys that are invalid as XML element names.

en	Example 3: Search = '^(?<number>\\d+) (?<text>.+?)\\$' / Replace = '_\\$+{text}_\\$+{number}' turns '16 elementname' into '_elementname_16'.

en	If modifiers are desired they have to be specified within the regexes themselves.

en	Regular expressions defined here will be applied before the XSLT mapping.

en	Regular expressions defined here will be applied after the XSLT mapping.

en	This OTRS operation backend module will be called internally to process the request, generating data for the response.

en	The request data will be processed by this mapping, to transform it to the kind of data OTRS expects.

en	The response data will be processed by this mapping, to transform it to the kind of data the remote system expects.

en	Route mapping for Operation

en	Define the route that should get mapped to this operation. Variables marked by a ':' will get mapped to the entered name and passed along with the others to the mapping. (e.g. /Ticket/:TicketID).

en	Valid request methods for Operation

en	Limit this Operation to specific request methods. If no method is selected all requests will be accepted.

en	Here you can specify the maximum size (in bytes) of REST messages that OTRS will process.

en	This configuration defines if incoming connections should get closed or kept alive.

en	URI to indicate specific location for accessing a web service.

en	Timeout value for requests.

en	An optional authentication mechanism to access the remote system.

en	Show or hide Proxy options to connect to the remote system.

en	Skip proxy servers that might be configured globally?

en	The password to open the SSL certificate if the key is encrypted.

en	Certification Authority (CA) Certificate

en	The full path and name of the certification authority certificate file that validates SSL certificate.

en	Certification Authority (CA) Directory

en	The full path of the certification authority directory where the CA certificates are stored in the file system.

en	The controller that the invoker should send requests to. Variables marked by a ':' will get replaced by the data value and passed along with the request. (e.g. /Ticket/:TicketID?UserLogin=:UserLogin&Password=:Password).

en	Set to "Yes" in order to send a filled SOAPAction header.

en	Set to "Yes" in order to check the received SOAPAction header (if not empty).

en	Set to "No" in order to ignore the received SOAPAction header.

en	Select how SOAPAction should be constructed.

en	Some web services require a specific construction.

en	Some web services send a specific construction.

en	Character to use as separator between name space and SOAP operation.

en	Usually .Net web services use "/" as separator.

en	Text to be used to as SOAPAction.

en	URI to give SOAP methods a context, reducing ambiguities.

en	Request name scheme

en	Select how SOAP request function wrapper should be constructed.

en	'FreeText' is used as example for actual configured value.

en	Request name free text

en	Text to be used to as function wrapper name suffix or replacement.

en	Please consider XML element naming restrictions (e.g. don't use '<' and '&').

en	Response name scheme

en	Select how SOAP response function wrapper should be constructed.

en	Response name free text

en	Here you can specify the maximum size (in bytes) of SOAP messages that OTRS will process.

en	Add new first level element

en	Outbound sort order for xml fields (structure starting below function name wrapper) - see documentation for SOAP transport.

en	The file must be a valid web service configuration YAML file.

en	Here you can specify a name for the webservice. If this field is empty, the name of the configuration file is used as name.

en	Ready2Adopt Web Services

en	Here you can activate Ready2Adopt web services showcasing our best practices that are a part of %s.

en	Please note that these web services may depend on other modules only available with certain %s contract levels (there will be a notification with further details when importing).

en	Import Ready2Adopt web service

en	Would you like to benefit from web services created by experts? Upgrade to %s to import some sophisticated Ready2Adopt web services.

en	After you save the configuration you will be redirected again to the edit screen.

en	If you want to return to overview please click the "Go to overview" button.

en	Error Handling Modules

en	Error handling modules are used to react in case of errors during the communication. Those modules are executed in a specific order, which can be changed by drag and drop.

en	Add error handling module

en	Operations are individual system functions which remote systems can request.

en	Invokers prepare data for a request to a remote web service, and process its response data.

en	At least one %s has a controller that is either not active or not present, please check the controller registration or delete the %s

en	Here you can view older versions of the current web service's configuration, export or even restore them.

en	If your account is marked as trusted, the X-OTRS headers already existing at arrival time (for priority etc.) will be kept and used, for example in PostMaster filters.

en	Outgoing email can be configured via the Sendmail* settings in %s.

en	Here you can upload a configuration file to import Ticket Notifications to your system. The file needs to be in .yml format as exported by the Ticket Notification module.

en	Here you can choose which events will trigger this notification. An additional ticket filter can be applied below to only send for ticket with certain criteria.

en	If ArticleCreate or ArticleSend is used as a trigger event, you need to specify an article filter as well. Please select at least one of the article filter fields.

en	This field is required and must have less than 4000 characters.

en	Use comma or semicolon to separate email addresses.

en	Downgrade to ((OTRS)) Community Edition

en	%s makes contact regularly with cloud.otrs.com to check on available updates and the validity of the underlying contract.

en	Unauthorized Usage Detected

en	This system uses the %s without a proper license! Please make contact with %s to renew or activate your contract!

en	You can either reinstall your current version or perform an update with the buttons below (update recommended).

en	An update for your %s is available! Please update at your earliest!

en	Your ((OTRS)) Community Edition is the base for all future actions. Please register first before you continue with the upgrade process of %s!

en	Before you can benefit from %s, please contact %s to get your %s contract.

en	Please visit our customer portal and file a request.

en	Everything else will be done as part of your contract.

en	You will receive updates about relevant security issues.

en	You will receive updates for all other relevant OTRS issues

en	You are about to downgrade to ((OTRS)) Community Edition and will lose the following features and all data related to these:

en	Faulty PGP configuration

en	Go to updating instructions

en	Package installation requires a patch level update of OTRS.

en	Package update requires a patch level update of OTRS.

en	You will receive updates for all other relevant OTRS issues.

en	How can I do a patch level update if I don’t have a contract?

en	Please find all relevant information within the updating instructions at %s.

en	In case you would have further questions we would be glad to answer them.

en	Please make sure your database accepts packages over %s MB in size (it currently only accepts packages up to %s MB). Please adapt the max_allowed_packet setting of your database in order to avoid errors.

en	Features for %s customers only

en	With %s, you can benefit from the following optional features. Please make contact with %s if you need more information.

en	Filter for PostMaster Filters

en	Filter for PostMaster filters

en	You can also use named captures %s and use the names in the 'Set' action %s (e.g. Regexp: %s, Set action: %s). A matched EMAILADDRESS has the name '%s'.

en	This priority is present in a SysConfig setting, confirmation for updating settings to point to the new priority is needed!

en	This priority is used in the following config settings:

en	Filter for processes

en	Ready2Adopt Processes

en	Here you can activate Ready2Adopt processes showcasing our best practices. Please note that some additional configuration may be required.

en	Would you like to benefit from processes created by experts? Upgrade to %s to import some sophisticated Ready2Adopt processes.

en	Import Ready2Adopt process

en	The selected required lock does not exist.

en	You can start a connection between two Activities by dropping the Transition element over the Start Activity of the connection. After that you can move the loose end of the arrow to the End Activity.

en	Actions can be assigned to a Transition by dropping the Action Element onto the label of a Transition.

en	Queue Management

en	This queue is present in a SysConfig setting, confirmation for updating settings to point to the new queue is needed!

en	To use a sign key, PGP keys or S/MIME certificates need to be added with identifiers for selected queue system address.

en	Filter for templates

en	You will receive updates about relevant security releases.

en	With your system registration we can improve our services for you, because we have all relevant information available.

en	This is only the beginning!

en	We will inform you about our new services and offerings soon.

en	Is it possible to deregister?

en	You can deregister at any time.

en	Which data is transfered when registering?

en	A registered system sends the following data to OTRS Group:

en	Fully Qualified Domain Name (FQDN), OTRS version, Database, Operating System and Perl version.

en	Why do I have to provide a description for my system?

en	The description of the system is optional.

en	The description and system type you specify help you to identify and manage the details of your registered systems.

en	How often does my OTRS system send updates?

en	Your system will send updates to the registration server at regular intervals.

en	Typically this would be around once every three days.

en	If you deregister your system, you will lose these benefits:

en	You need to log in with your OTRS-ID to deregister your system.

en	Retrieve a new one

en	This data will be frequently transferred to OTRS Group when you register this system.

en	Optional description of this system.

en	Continuing with this step will deregister the system from OTRS Group.

en	You can modify registration settings here.

en	There is no data regularly sent from your system to %s.

en	The following data is sent at minimum every 3 days from your system to %s.

en	The data will be transferred in JSON format via a secure https connection.

en	Filter for agents

en	To be able to use SMIME in OTRS, you have to enable it first.

en	To show certificate details click on a certificate icon.

en	To manage private certificate relations click on a private key icon.

en	Here you can add relations to your private certificate, these will be embedded to the S/MIME signature every time you use this certificate to sign an email.

en	Only select queries are allowed.

en	There is at least one parameter missing for the binding. Please check it.

en	Detail Session View for %s (%s)

en	Detail View for SessionID: %s - %s

en	It's not possible to invalidate this entry because there is no other merge states in system!

en	This system address cannot be set to invalid.

en	This system address cannot be set to invalid, because it is used in one or more queue(s) or auto response(s).

en	There are currently no settings available. Please make sure to run 'otrs.Console.pl Maint::Config::Rebuild' before using the software.

en	This is an overview of all settings which will be part of the deployment if you start it now. You can compare each setting to its former state by clicking the icon on the top right.

en	To exclude certain settings from a deployment, click the checkbox on the header bar of a setting.

en	There are %s changed settings which will be deployed in this run.

en	Switch to basic mode to deploy settings only changed by you.

en	Switch to advanced mode to deploy settings changed by other users, too.

en	Go back to Deployment Details

en	Some time before this system maintenance starts the users will receive a notification on each screen announcing about this fact.

en	This field must have less then 250 characters.

en	Kill all Sessions, except for your own

en	Template Management

en	A standard template with this name already exists!

en	To get the first 20 characters of the subject of the current/latest agent article (current for Answer and Forward, latest for Note template type). This tag is not supported for other template types.

en	To get the first 5 lines of the body of the current/latest agent article (current for Answer and Forward, latest for Note template type). This tag is not supported for other template types.

en	To get the first 20 characters of the subject of the current/latest article (current for Answer and Forward, latest for Note template type). This tag is not supported for other template types.

en	To get the first 5 lines of the body of the current/latest article (current for Answer and Forward, latest for Note template type). This tag is not supported for other template types.

en	Manage Template-Attachment Relations

en	This type is present in a SysConfig setting, confirmation for updating settings to point to the new type is needed!

en	This type is used in the following config settings:

en	A user with this username already exists!

en	Effective Permissions for Agent

en	Table above shows effective group permissions for the agent. The matrix takes into account all inherited permissions (e.g. via roles).

en	Please set this to value before End date.

en	Please set this to value after Start date.

en	Relative point of time

en	The customer user is already selected in the ticket mask.

en	The OTRS Daemon is a daemon process that performs asynchronous tasks, e.g. ticket escalation triggering, email sending, etc.

en	A running OTRS Daemon is mandatory for correct system operation.

en	Make sure that the file '%s' exists (without .dist extension). This cron job will check every 5 minutes if the OTRS Daemon is running and start it if needed.

en	Execute '%s start' to make sure the cron jobs of the 'otrs' user are active.

en	After 5 minutes, check that the OTRS Daemon is running in the system ('bin/otrs.Daemon.pl status').

en	Unauthorized usage of %s detected

en	If you decide to downgrade to ((OTRS)) Community Edition, you will lose all database tables and data related to %s.

en	Please note: you're currently editing the preferences of %s.

en	Avatars have been disabled by the system administrator. You'll see your initials instead.

en	This setting can currently not be saved.

en	This address is registered as system address and cannot be used: %s

en	Please include at least one customer user for the ticket.

en	Select this customer as the main customer.

en	Ticket %s: first response time is over (%s/%s)!

en	Ticket %s: first response time will be over in %s/%s!

en	Ticket %s: update time is over (%s/%s)!

en	Ticket %s: update time will be over in %s/%s!

en	Ticket %s: solution time is over (%s/%s)!

en	Ticket %s: solution time will be over in %s/%s!

en	Try typing part of the ticket number or title in order to search by it.

en	Limit the search to tickets with same Customer ID (%s).

en	No more events found. Please try changing the filter settings.

en	This message is being processed. Already tried to send %s time(s). Next try will be %s.

en	Note: Type is invalid!

en	Preview of this article is not possible because %s channel is missing in the system.

en	This feature is part of the %s. Please contact us at %s for an upgrade.

en	Please re-install %s package in order to display this article.

en	To protect your privacy, remote content was blocked.

en	Yes, I accept your license.

en	The customer ID is not changeable, no other customer ID can be assigned to this ticket.

en	First select a customer user, then you can select a customer ID to assign to this ticket.

en	Select a customer ID to assign to this ticket.

en	%s detected possible network issues. You could either try reloading this page manually or wait until your browser has re-established the connection on its own.

en	The connection has been re-established after a temporary connection loss. Due to this, elements on this page could have stopped to work correctly. In order to be able to use all elements correctly again, it is strongly recommended to reload this page.

en	In order to experience this software, you'll need to enable JavaScript in your browser.

en	This software runs with a huge lists of browsers, please upgrade to one of these.

en	One moment please, you are being redirected...

en	2 Factor Token

en	Your 2 Factor Token

en	How we should address you

en	With %s, our experts take care of correct installation and cover your back with support and periodic security updates.

en	Click to delete this attachment.

en	Germany

en	United States

en	Mexico

en	Hungary

en	Brazil

en	Singapore

en	Hong Kong

en	Accept license and continue

en	Scale preview content

en	Open URL in new tab

en	A preview of this website can't be provided because it didn't allow to be embedded.

en	Feature not Available

en	Sorry, but this feature of OTRS is currently not available for mobile devices. If you'd like to use it, you can either switch to desktop mode or use your regular desktop device.

en	This is the message of the day. You can edit this in %s.

en	The file is not an image that can be shown inline!

en	No user configurable notifications found.

en	This is the default public interface of OTRS! There was no action parameter given.

en	You could install a custom public module (via the package manager), for example the FAQ module, which has a public interface.

en	The past complete %s and the current+upcoming complete %s %s

en	Configurable Params of Static Stat

en	Defines the time unit that will be used to split the selected time period into reporting data points.

en	This setting is currently being overridden in %s and can't thus be changed here!

en	Changing this setting is only available in a higher config level!

en	%s (%s) is currently working on this setting.

en	With %s, System Configuration supports versioning, rollback and user-specific configuration settings.

en	Click to select a file for upload.

en	This field can have no more than 250 characters.

en	Reset setting on global level.

en	Reset globally

en	Remove all user changes.

en	Reset locally

en	user(s) have modified this setting.

en	Do you really want to reset this setting to it's default value?

en	You can use the category selection to limit the navigation tree below to entries from the selected category. As soon as you select the category, the tree will be re-built.

en	ACLs could not be Imported due to a unknown error, please check OTRS logs for more information

en	There was an error setting the entity sync status.

en	There was an error getting data for ACL with ID %s

en	%s (copy) %s

en	System was unable to import file!

en	Please check the log for more information.

en	Notification name already exists!

en	There was an error getting data for Notification with ID:%s!

en	Unknown Notification %s!

en	%s (copy)

en	There was an error creating the Notification

en	Notifications could not be Imported due to a unknown error, please check OTRS logs for more information

en	There where errors adding/updating the following Notifications: %s. Please check the log file for more information.

en	Notification updated!

en	All agents with (at least) read permission for the appointment (calendar)

en	All agents with write permission for the appointment (calendar)

en	Yes, but require at least one active notification method.

en	Invalid CommunicationID!

en	Invalid StartTime: %s!

en	Dynamic field %s not found!

en	Unable to set value for dynamic field %s!

en	No configuration for 'CustomerGroupPermissionContext' found!

en	Please check system configuration.

en	Invalid permission context configuration:

en	Change Customer User Relations for Group

en	Change Group Relations for Customer User

en	Allocate Services to Customer User

en	Fields configuration is not valid

en	Objects configuration is not valid

en	Add %s field

en	The field does not contain only ASCII letters and numbers.

en	There is another field with the same name.

en	The field must be numeric.

en	Change %s field

en	The name for this field should not change.

en	Could not update the field %s

en	Prevent entry of dates in the future

en	Prevent entry of dates in the past

en	This field value is duplicated.

en	Select at least one recipient.

en	Got no values to check.

en	Please remove the following words because they cannot be used for the ticket selection:

en	Communication type needs to be 'Requester' or 'Provider'!

en	Invalid Subaction!

en	Need ErrorHandlingType!

en	ErrorHandlingType %s is not registered

en	Could not update web service

en	Need ErrorHandling

en	Could not determine config for error handler %s

en	Invoker processing outgoing request data

en	Mapping outgoing request data

en	Transport processing request into response

en	Mapping incoming response data

en	Invoker processing incoming response data

en	Transport receiving incoming request data

en	Mapping incoming request data

en	Operation processing incoming request data

en	Mapping outgoing response data

en	Transport sending outgoing response data

en	skip same backend modules only

en	skip all modules

en	Operation deleted

en	MappingType %s is not registered

en	Could not get registered modules for Invoker

en	Could not get backend for Invoker %s

en	The event %s is not valid.

en	Could not update configuration data for WebserviceID %s

en	This sub-action is not valid

en	Regexp

en	Validation Module

en	Simple Mapping for Outgoing Data

en	Simple Mapping for Incoming Data

en	Could not get registered configuration for action type %s

en	Could not get backend for %s %s

en	Map to (use provided value as default)

en	Exact value(s)

en	Ignore (drop Value/value pair)

en	XSLT Mapping for Outgoing Data

en	XSLT Mapping for Incoming Data

en	Outgoing request data before processing (RequesterRequestInput)

en	Outgoing request data before mapping (RequesterRequestPrepareOutput)

en	Outgoing request data after mapping (RequesterRequestMapOutput)

en	Incoming response data before mapping (RequesterResponseInput)

en	Outgoing error handler data after error handling (RequesterErrorHandlingOutput)

en	Incoming request data before mapping (ProviderRequestInput)

en	Incoming request data after mapping (ProviderRequestMapOutput)

en	Outgoing response data before mapping (ProviderResponseInput)

en	Outgoing error handler data after error handling (ProviderErrorHandlingOutput)

en	Could not determine config for operation %s

en	OperationType %s is not registered

en	Could not load %s.

en	The imported file has not valid YAML content! Please check OTRS log for details

en	Got no WebserviceHistoryID!

en	Could not get history data for WebserviceHistoryID %s

en	Email account fetch already fetched by another process. Please try again later!

en	Customer user of the ticket

en	Invisible to customer

en	Visible to customer

en	Sorry, Apache::Reload is needed as PerlModule and PerlInitHandler in Apache config file. See also scripts/apache2-httpd.include.conf. Alternatively, you can use the command line tool bin/otrs.Console.pl to install packages!

en	No packages found in selected repository. Please check log for more info!

en	Package not verified due a communication issue with verification server!

en	Yes (mandatory)

en	Unknown Process %s!

en	There was an error generating a new EntityID for this Process

en	There was an error creating the Process

en	There was an error setting the entity sync status for Process entity: %s

en	Could not get data for ProcessID %s

en	There was an error updating the Process

en	Process: %s could not be deleted

en	There was an error synchronizing the processes.

en	The %s:%s is still in use

en	The %s:%s has a different EntityID

en	Could not delete %s:%s

en	There was an error setting the entity sync status for %s entity: %s

en	Process: %s is not Inactive

en	There was an error generating a new EntityID for this Activity

en	There was an error creating the Activity

en	There was an error setting the entity sync status for Activity entity: %s

en	Could not get data for ActivityID %s

en	There was an error updating the Activity

en	Missing Parameter: Need Activity and ActivityDialog!

en	ActivityDialog already assigned to Activity. You cannot add an ActivityDialog twice!

en	Error while saving the Activity to the database!

en	There was an error generating a new EntityID for this ActivityDialog

en	There was an error setting the entity sync status for ActivityDialog entity: %s

en	Edit Activity Dialog "%s"

en	There was an error setting the entity sync status for Transition entity: %s

en	At least one valid config parameter is required.

en	There was an error setting the entity sync status for TransitionAction entity: %s

en	Error: Not all keys seem to have values or vice versa.

en	CAFingerprint must be different than CertFingerprint

en	Handle Private Certificate Relations

en	There are no invalid settings active at this time.

en	You currently don't have any favourite settings.

en	The following settings could not be found: %s

en	System Configuration could not be imported due to an unknown error, please check OTRS logs for more information.

en	Some imported settings are not present in the current state of the configuration or it was not possible to update them. Please check the OTRS log for more information.

en	You need to enable the setting before locking!

en	You can't work on this setting because %s (%s) is currently working on it.

en	+%s more

en	No RecipientField is given!

en	No preferences for %s!

en	Can't get element data of %s!

en	Can't get filter content data of %s!

en	System was unable to deploy your changes.

en	System was unable to reset the setting!

en	Could not perform validation on field %s!

en	The following tickets were ignored because they are locked by another agent or you don't have write access to tickets: %s.

en	The following ticket was ignored because it is locked by another agent or you don't have write access to ticket: %s.

en	The following tickets were ignored because they are locked by another agent or you don't have write access to these tickets: %s.

en	The following tickets were locked: %s.

en	Article subject will be empty if the subject contains only the ticket hook!

en	Can't read plain article! Maybe there is no plain email in backend! Read backend message.

en	Couldn't get ActivityDialogEntityID "%s"!

en	Parameter %s is missing in %s.

en	No ActivityDialog configured for %s in _RenderAjax!

en	Got no Start ActivityEntityID or Start ActivityDialogEntityID for Process: %s in _GetParam!

en	Couldn't get Ticket for TicketID: %s in _GetParam!

en	Process::Default%s Config Value missing!

en	Got no ProcessEntityID or TicketID and ActivityDialogEntityID!

en	Can't get StartActivityDialog and StartActivityDialog for the ProcessEntityID "%s"!

en	Can't get Ticket "%s"!

en	Can't get ProcessEntityID or ActivityEntityID for Ticket "%s"!

en	Can't get Activity configuration for ActivityEntityID "%s"!

en	Can't get ActivityDialog configuration for ActivityDialogEntityID "%s"!

en	Can't get data for Field "%s" of ActivityDialog "%s"!

en	PendingTime can just be used if State or StateID is configured for the same ActivityDialog. ActivityDialog: %s!

en	Couldn't get Config for ActivityDialogEntityID "%s"!

en	Missing ProcessEntityID, check your ActivityDialogHeader.tt!

en	No StartActivityDialog or StartActivityDialog for Process "%s" configured!

en	Couldn't create ticket for Process with ProcessEntityID "%s"!

en	Could not store ActivityDialog, invalid TicketID: %s!

en	Invalid TicketID: %s!

en	This step does not belong anymore to the current activity in process for ticket '%s%s%s'! Another user changed this ticket in the meantime. Please close this window and reload the ticket.

en	Wrong ActivityDialog Field config: %s can't be Display => 1 / Show field (Please change its configuration to be Display => 0 / Do not show field or Display => 2 / Show field as mandatory)!

en	Could not set %s for Ticket with ID "%s" in ActivityDialog "%s"!

en	Untitled

en	Feature not enabled!

en	Feature is not active

en	Outgoing Email (internal)

en	Escalation Update Time In Effect

en	Escalation Response Time In Effect

en	Notification Was Sent

en	This ticket does not exist, or you don't have permissions to access it in its current state.

en	Event type filter settings were saved.

en	Fields with no group

en	Invisible only

en	Visible only

en	Visible and invisible

en	Article could not be opened! Perhaps it is on another article page?

en	Show Ticket Timeline View

en	Show Ticket Timeline View (%s)

en	Got no FormID.

en	Error: the file could not be deleted properly. Please contact your administrator (missing FileID).

en	ArticleID is needed!

en	No TicketID for ArticleID (%s)!

en	You don't have sufficient permissions for ticket creation in default queue.

en	Please remove the following words because they cannot be used for the search:

en	If you want to re-run the Installer, disable the SecureMode in the SysConfig.

en	Error: Please make sure your database accepts packages over %s MB in size (it currently only accepts packages up to %s MB). Please adapt the max_allowed_packet setting of your database in order to avoid errors.

en	Wrong database collation (%s is %s, but it needs to be utf8).

en	Sent message encrypted to recipient!

en	There are no encryption keys available for the addresses: '%s'.

en	There are no selected encryption keys for the addresses: '%s'.

en	Cannot use expired encryption keys for the addresses: '%s'.

en	Cannot use revoked encryption keys for the addresses: '%s'.

en	Encrypt

en	Keys/certificates will only be shown for recipients with more than one key/certificate. The first found key/certificate will be pre-selected. Please make sure to select the correct one.

en	Email security

en	PGP sign

en	PGP sign and encrypt

en	PGP encrypt

en	SMIME sign

en	SMIME sign and encrypt

en	SMIME encrypt

en	Cannot use expired signing key: '%s'.

en	Cannot use revoked signing key: '%s'.

en	There are no signing keys available for the addresses '%s'.

en	There are no selected signing keys for the addresses '%s'.

en	Keys/certificates will only be shown for a sender with more than one key/certificate. The first found key/certificate will be pre-selected. Please make sure to select the correct one.

en	Shown customer ids

en	The start time of a ticket has been set after the end time!

en	User set their status to unavailable.

en	The following tickets are not updated: %s.

en	This ticket does not exist, or you don't have permissions to access it in its current state. You can take one of the following actions:

en	Please verify your license data!

en	System maintenance is active!

en	A system maintenance period will start at: %s and is expected to stop at: %s

en	The installation of packages which are not verified by the OTRS Group is activated. These packages could threaten your whole system! It is recommended not to use unverified packages.

en	You have %s invalid setting(s) deployed. Click here to show invalid settings.

en	Please make sure you've chosen at least one transport method for mandatory notifications.

en	Please specify an end date that is after the start date.

en	This password is forbidden by the current system configuration. Please contact the administrator if you have additional questions.

en	No past complete or the current+upcoming complete relative time value selected.

en	The selected time period is larger than the allowed time period.

en	Please select only one element or allow modification at stat generation time.

en	Please select at least one value of this field or allow modification at stat generation time.

en	Please provide a value or allow modification at stat generation time.

en	Please remove the following words because they cannot be used for the ticket restrictions: %s.

en	Couldn't read ACL configuration file. Please make sure the file is valid.

en	You have exceeded the number of concurrent agents - contact sales@otrs.com.

en	Skip notification delivery

en	This setting is not visible.

en	This setting can be overridden in the user preferences.

en	This setting can be overridden in the user preferences, but is not active by default.

en	Customer user "%s" already exists.

en	This email address is already in use for another customer user.

en	Ignore this field.

en	Couldn't read Notification configuration file. Please make sure the file is valid.

en	Imported notification has body text with more than 4000 characters.

en	File is different!

en	The installation of packages which are not verified by the OTRS Group is not possible by default. You can activate the installation of not verified packages via the "AllowNotVerifiedPackages" system configuration setting.

en	The process "%s" and all of its data has been imported successfully.

en	Historic Time Range

en	Solution Average (affected by escalation configuration)

en	Solution Min Time (affected by escalation configuration)

en	Solution Max Time (affected by escalation configuration)

en	Solution Working Time Average (affected by escalation configuration)

en	Solution Min Working Time (affected by escalation configuration)

en	Solution Max Working Time (affected by escalation configuration)

en	First Response Average (affected by escalation configuration)

en	First Response Min Time (affected by escalation configuration)

en	First Response Max Time (affected by escalation configuration)

en	First Response Working Time Average (affected by escalation configuration)

en	First Response Min Working Time (affected by escalation configuration)

en	First Response Max Working Time (affected by escalation configuration)

en	Number of Tickets (affected by escalation configuration)

en	Outdated Tables

en	Outdated tables were found in the database. These can be removed if empty.

en	This character set is not yet supported, please see https://bugs.otrs.org/show_bug.cgi?id=12361. Please convert your database to the character set 'utf8'.

en	The setting character_set_database needs to be 'utf8'.

en	There were tables found which do not have 'utf8' as charset.

en	Tables with invalid default values were found. In order to fix it automatically, please run: bin/otrs.Console.pl Maint::Database::Check --repair

en	The setting 'max_allowed_packet' must be higher than 64 MB.

en	Primary Key Sequences and Triggers

en	The following sequences and/or triggers with possible wrong names have been found. Please rename them manually.

en	Primary Key Sequences

en	The following sequences with possible wrong names have been found. Please rename them manually.

en	PostgreSQL 9.2 or higher is required.

en	Perl Modules Audit

en	CPAN::Audit reported that one or more installed Perl modules have known vulnerabilities. Please note that there might be false positives for distributions patching Perl modules without changing their version number.

en	CPAN::Audit did not report any known vulnerabilities in the installed Perl modules.

en	Indexed Articles

en	No connections found.

en	ok

en	permanent connection errors

en	intermittent connection errors

en	Legacy configuration backup files found in Kernel/Config/Backups folder, but they might still be required by some packages.

en	Legacy configuration backup files are no longer needed for the installed packages, please remove them from Kernel/Config/Backups folder.

en	Session Config Settings

en	Invalid Users with Locked Tickets

en	There are invalid users with locked tickets.

en	The indexing process forces the storage of the original article text in the article search index, without executing filters or applying stop word lists. This will increase the size of the search index and thus may slow down fulltext searches.

en	Agents using favourites for the admin overview

en	Support Data Collection

en	Support data could not be collected from the web server.

en	Could not combine settings values into a perl hash.

en	Can not lock the deployment for UserID '%s'!

en	Value is not correct! Please, consider updating this field.

en	Value doesn't satisfy regex (%s).

en	Value is not correct! Please, consider updating this module.

en	Chat Participant

en	Authentication succeeded, but no user data record is found in the database. Please contact the administrator.

en	Added via Customer Panel (%s)

en	Can't send account info!

en	Action "%s" not found!

en	Customer removed ticket.

en	Follow-ups for closed tickets are not possible. A new ticket will be created.

en	Automatic reply which will be sent out after a new ticket has been created.

en	Automatic reject which will be sent out after a follow-up has been rejected (in case queue follow-up option is "reject").

en	Automatic confirmation which is sent out after a follow-up has been received for a ticket (in case queue follow-up option is "possible").

en	Automatic response which will be sent out after a follow-up has been rejected and a new ticket has been created (in case queue follow-up option is "new ticket").

en	Auto remove will be sent out after a customer removed the request.

en	default reply (after new ticket has been created)

en	default reject (after follow-up and rejected of a closed ticket)

en	default follow-up (after a ticket follow-up has been added)

en	default reject/new ticket created (after closed follow-up with new ticket creation)

en	tmp_lock

en	You will receive a notification if a customer sends a follow-up to an unlocked ticket which is in your "My Queues" or "My Services".

en	You will receive a notification if a customer sends a follow-up to a locked ticket of which you are the ticket owner or responsible.

en	You will receive a notification as soon as a ticket owned by you is automatically unlocked.

en	You will receive a notification each time a reminder time is reached for one of your appointments.

en	Error during AJAX communication. Status: %s, Error: %s

en	This window must be called from compose window.

en	Remove this dynamic field

en	Do you really want to delete this generic agent job?

en	Delete error handling module

en	It is not possible to add a new event trigger because the event is not set.

en	Sorry, the only existing condition can't be removed.

en	Sorry, the only existing field can't be removed.

en	Delete conditions

en	Mapping for Key %s

en	Mapping for Key

en	Delete this Mail Account

en	Deleting the mail account and its data. This may take a while...

en	Do you really want to delete this key?

en	There is a package upgrade process running, click here to see status information about the upgrade progress.

en	No response from get package upgrade result.

en	No response from package upgrade all.

en	No response from get package upgrade run status.

en	Customer interface does not support articles not visible for customers.

en	Do you really want to delete this certificate?

en	Support Data information was successfully sent.

en	It is not possible to set this entry to invalid. All affected configuration settings have to be changed beforehand.

en	Cannot proceed

en	You can either have the affected settings updated automatically to reflect the changes you just made or do it on your own by pressing 'update manually'.

en	Save and update automatically

en	Don't save, update manually

en	The item you're currently viewing is part of a not-yet-deployed configuration setting, which makes it impossible to edit it in its current state. Please wait until the setting has been deployed. If you're unsure what to do next, please contact your system administrator.

en	Unfortunately deploying is currently not possible, maybe because another agent is already deploying. Please try again later.

en	There was an error. Please save all settings you are editing and check the logs for more information.

en	Reset option is required!

en	By restoring this deployment all settings will be reverted to the value they had at the time of the deployment. Do you really want to continue?

en	Keys with values can't be renamed. Please remove this key/value pair instead and re-add it afterwards.

en	Unlock setting.

en	Deleting the template and its data. This may take a while...

en	Please either turn some off first or increase the limit in configuration.

en	Are you sure you want to delete this appointment? This operation cannot be undone.

en	First select a customer user, then select a customer ID to assign to this ticket.

en	It is going to be deleted from the field, please try again.

en	Please check the fields marked as red for valid inputs.

en	Do you really want to delete this link?

en	Please note that at least one of the settings you have changed requires a page reload. Click here to reload the current screen.

en	Please remove the following words from your search as they cannot be searched for:

en	Generate

en	...and %s more

en	Reload page (%ss)

en	Namespace %s could not be initialized, because %s could not be found.

en	An error occurred! Please check the browser error log for more details!

en	Please add values for all keys before saving the setting.

en	A key with this name ('%s') already exists.

en	Do you really want to revert this setting to its historical value?

en	Invalid date (need a past date)!

en	Not available

en	Show current selection

en	Current selection

en	Ascending sort applied,

en	Descending sort applied,

en	No sort applied,

en	sorting is disabled

en	activate to apply an ascending sort

en	activate to apply a descending sort

en	activate to remove the sort

en	Please only select one file for upload.

en	Sorry, you can only upload one file here.

en	Sorry, you can only upload %s files.

en	Please only select at most %s files for upload.

en	The following files are not allowed to be uploaded: %s

en	The following files exceed the maximum allowed size per file of %s and were not uploaded: %s

en	The following files were already uploaded and have not been uploaded again: %s

en	No space left for the following files: %s

en	Available space %s of %s.

en	Upload information

en	An unknown error occurred when deleting the attachment. Please try again. If the error persists, please contact your system administrator.

en	This is %s

en	Complex %s with %s arguments

en	No Data Available.

en	Grouped

en	Stacked

en	"Slim" skin which tries to save screen space for power users.

en	(UserLogin) Lastname Firstname

en	2 - Enabled by default

en	Activates support for customer and customer user groups.

en	Added %s time unit(s), for a total of %s time unit(s).

en	Added follow-up to ticket [%s]. %s

en	Added note (%s).

en	Added phone call from customer.

en	Added phone call to customer.

en	Added system request (%s).

en	Added web request from customer.

en	Adds customers email addresses to recipients in the ticket compose screen of the agent interface. The customers email address won't be added if the article type is email-internal.

en	Adds the one time vacation days for the indicated calendar.

en	Adds the one time vacation days.

en	Adds the permanent vacation days for the indicated calendar.

en	Adds the permanent vacation days.

en	Admin Area.

en	Agent Name

en	Agent Name + FromSeparator + System Address Display Name

en	Agent Preferences.

en	Agent interface module to access CIC search via nav bar. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Agent interface module to access fulltext search via nav bar. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Agent interface module to access search profiles via nav bar. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Agent interface notification module to see the number of locked tickets. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Agent interface notification module to see the number of tickets an agent is responsible for. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Agent interface notification module to see the number of watched tickets. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Allows adding notes in the close ticket screen of the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows adding notes in the ticket free text screen of the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows adding notes in the ticket note screen of the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows adding notes in the ticket owner screen of a zoomed ticket in the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows adding notes in the ticket pending screen of a zoomed ticket in the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows adding notes in the ticket priority screen of a zoomed ticket in the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows adding notes in the ticket responsible screen of the agent interface. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Allows customers to set the ticket queue in the customer interface. If this is not enabled, QueueDefault should be configured.

en	Allows customers to set the ticket type in the customer interface. If this is not enabled, TicketTypeDefault should be configured.

en	Allows default services to be selected also for non existing customers.

en	Allows extended search conditions in ticket search of the agent interface. With this feature you can search e. g. ticket title with this kind of conditions like "(*key1*&&*key2*)" or "(*key1*||*key2*)".

en	Allows extended search conditions in ticket search of the customer interface. With this feature you can search e. g. ticket title with this kind of conditions like "(*key1*&&*key2*)" or "(*key1*||*key2*)".

en	Allows extended search conditions in ticket search of the generic agent interface. With this feature you can search e. g. ticket title with this kind of conditions like "(*key1*&&*key2*)" or "(*key1*||*key2*)".

en	Allows generic agent to execute custom command line scripts.

en	Allows generic agent to execute custom modules.

en	Allows to save current work as draft in the close ticket screen of the agent interface.

en	Allows to save current work as draft in the email outbound screen of the agent interface.

en	Allows to save current work as draft in the ticket compose screen of the agent interface.

en	Allows to save current work as draft in the ticket forward screen of the agent interface.

en	Allows to save current work as draft in the ticket free text screen of the agent interface.

en	Allows to save current work as draft in the ticket move screen of the agent interface.

en	Allows to save current work as draft in the ticket note screen of the agent interface.

en	Allows to save current work as draft in the ticket owner screen of the agent interface.

en	Allows to save current work as draft in the ticket pending screen of the agent interface.

en	Allows to save current work as draft in the ticket phone inbound screen of the agent interface.

en	Allows to save current work as draft in the ticket phone outbound screen of the agent interface.

en	Allows to save current work as draft in the ticket priority screen of the agent interface.

en	Allows to save current work as draft in the ticket responsible screen of the agent interface.

en	Always show RichText if available

en	Appointment calendar event module that prepares notification entries for appointments.

en	Appointment calendar event module that updates the ticket with data from ticket appointment.

en	Arabic (Saudi Arabia)

en	ArticleTree

en	Automatically change the state of a ticket with an invalid owner once it is unlocked. Maps from a state type to a new ticket state.

en	Automatically lock and set owner to current Agent after opening the move ticket screen of the agent interface.

en	Automatically sets the owner of a ticket as the responsible for it (if ticket responsible feature is enabled). This will only work by manually actions of the logged in user. It does not work for automated actions e.g. GenericAgent, Postmaster and GenericInterface.

en	Balanced white skin by Felix Niklas (slim version).

en	Based on global RichText setting

en	Basic fulltext index settings. Execute "bin/otrs.Console.pl Maint::Ticket::FulltextIndex --rebuild" in order to generate a new index.

en	Cache time in seconds for agent authentication in the GenericInterface.

en	Cache time in seconds for customer authentication in the GenericInterface.

en	Cache time in seconds for the DB ACL backend.

en	Cache time in seconds for the DB process backend.

en	Cache time in seconds for the SSL certificate attributes.

en	Cache time in seconds for the web service config backend.

en	Catalan

en	Change the responsible for this ticket

en	Changed SLA to "%s" (%s).

en	Changed archive state to "%s".

en	Changed customer to "%s".

en	Changed dynamic field %s from "%s" to "%s".

en	Changed owner to "%s" (%s).

en	Changed pending time to "%s".

en	Changed queue to "%s" (%s) from "%s" (%s).

en	Changed responsible to "%s" (%s).

en	Changed service to "%s" (%s).

en	Changed state from "%s" to "%s".

en	Changed title from "%s" to "%s".

en	Changed type from "%s" (%s) to "%s" (%s).

en	Checks for articles that needs to be updated in the article search index.

en	Checks for queued outgoing emails to be sent.

en	Checks if an E-Mail is a followup to an existing ticket by searching the subject for a valid ticket number.

en	Checks if an email is a follow-up to an existing ticket with external ticket number which can be found by ExternalTicketNumberRecognition filter module.

en	Checks the SystemID in ticket number detection for follow-ups. If not enabled, SystemID will be changed after using the system.

en	Chinese (Simplified)

en	Chinese (Traditional)

en	Choose for which kind of ticket changes you want to receive notifications. Please note that you can't completely disable notifications marked as mandatory.

en	Choose which notifications you'd like to receive.

en	Cloud service admin module registration for the transport layer.

en	Collect support data for asynchronous plug-in modules.

en	Columns that can be filtered in the escalation view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the locked view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the queue view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the responsible view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the service view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the status view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the ticket search result view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Columns that can be filtered in the watch view of the agent interface. Note: Only Ticket attributes, Dynamic Fields (DynamicField_NameX) and Customer attributes (e.g. CustomerUserPhone, CustomerCompanyName, ...) are allowed.

en	Comment2

en	Communication log limit per page for Communication Log Overview.

en	Company Tickets.

en	Company name which will be included in outgoing emails as an X-Header.

en	Compat module for AgentZoom to AgentTicketZoom.

en	Complex

en	Configure any additional readonly mirror databases that you want to use.

en	Configure sending of support data to OTRS Group for improved support.

en	Configures a default TicketDynamicField setting. "Name" defines the dynamic field which should be used, "Value" is the data that will be set, and "Event" defines the trigger event. Please check the developer manual (https://doc.otrs.com/doc/), chapter "Ticket Event Module".

en	Controls how to display the ticket history entries as readable values.

en	Controls if CustomerID is automatically copied from the sender address for unknown customers.

en	Controls if CustomerID is read-only in the agent interface.

en	Controls if more than one from entry can be set in the new phone ticket in the agent interface.

en	Controls if the admin is allowed to import a saved system configuration in SysConfig.

en	Controls if the admin is allowed to make changes to the database via AdminSelectBox.

en	Controls if the autocomplete field will be used for the customer ID selection in the AdminCustomerUser interface.

en	Controls if the ticket and article seen flags are removed when a ticket is archived.

en	Created ticket [%s] in "%s" with priority "%s" and state "%s".

en	Custom text for the page shown to customers that have no tickets yet (if you need those text translated add them to a custom translation module).

en	Customer Information Center search.

en	Customer Information Center.

en	Customer Ticket Print Module.

en	Customer User Information Center search.

en	Customer User Information Center.

en	Customer item (icon) which shows the closed tickets of this customer as info block. Setting CustomerUserLogin to 1 searches for tickets based on login name rather than CustomerID.

en	Customer item (icon) which shows the open tickets of this customer as info block. Setting CustomerUserLogin to 1 searches for tickets based on login name rather than CustomerID.

en	Customer preferences.

en	Customizable stop words for fulltext index. These words will be removed from the search index.

en	Default ProcessManagement entity prefixes for entity IDs that are automatically generated.

en	Default agent name

en	Default data to use on attribute for ticket search screen. Example: "TicketCreateTimePointFormat=year;TicketCreateTimePointStart=Last;TicketCreateTimePoint=2;".

en	Default data to use on attribute for ticket search screen. Example: "TicketCreateTimeStartYear=2010;TicketCreateTimeStartMonth=10;TicketCreateTimeStartDay=4;TicketCreateTimeStopYear=2010;TicketCreateTimeStopMonth=11;TicketCreateTimeStopDay=3;".

en	Default skin for the customer interface.

en	Define Actions where a settings button is available in the linked objects widget (LinkObject::ViewMode = "complex"). Please note that these Actions must have registered the following JS and CSS files: Core.AllocationList.css, Core.UI.AllocationList.js, Core.UI.Table.Sort.js, Core.Agent.TableFilters.js.

en	Define a mapping between variables of the customer user data (keys) and dynamic fields of a ticket (values). The purpose is to store customer user data in ticket dynamic fields. The dynamic fields must be present in the system and should be enabled for AgentTicketFreeText, so that they can be set/updated manually by the agent. They mustn't be enabled for AgentTicketPhone, AgentTicketEmail and AgentTicketCustomer. If they were, they would have precedence over the automatically set values. To use this mapping, you have to also activate the Ticket::EventModulePost###4100-DynamicFieldFromCustomerUser setting.

en	Define dynamic field name for end time. This field has to be manually added to the system as Ticket: "Date / Time" and must be activated in ticket creation screens and/or in any other ticket action screens.

en	Define dynamic field name for start time. This field has to be manually added to the system as Ticket: "Date / Time" and must be activated in ticket creation screens and/or in any other ticket action screens.

en	Define the max depth of queues.

en	Define the queue comment 2.

en	Define the service comment 2.

en	Define the sla comment 2.

en	Define which avatar default image should be used for the article view if no gravatar is assigned to the mail address. Check https://gravatar.com/site/implement/images/ for further information.

en	Define which avatar default image should be used for the current agent if no gravatar is assigned to the mail address of the agent. Check https://gravatar.com/site/implement/images/ for further information.

en	Define which avatar engine should be used for the agent avatar on the header and the sender images in AgentTicketZoom. If 'None' is selected, initials will be displayed instead. Please note that selecting anything other than 'None' will transfer the encrypted email address of the particular user to an external service.

en	Define which columns are shown in the linked appointment widget (LinkObject::ViewMode = "complex"). Possible settings: 0 = Disabled, 1 = Available, 2 = Enabled by default.

en	Define which columns are shown in the linked tickets widget (LinkObject::ViewMode = "complex"). Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Defines a filter to collect CVE numbers from article texts in AgentTicketZoom. The results will be displayed in a meta box next to the article. Fill in URLPreview if you would like to see a preview when moving your mouse cursor above the link element. This could be the same URL as in URL, but also an alternate one. Please note that some websites deny being displayed within an iframe (e.g. Google) and thus won't work with the preview mode.

en	Defines a permission context for customer to group assignment.

en	Defines a sleep time in microseconds between tickets while they are been processed by a job.

en	Defines all the languages that are available to the application. Specify only English names of languages here.

en	Defines all the languages that are available to the application. Specify only native names of languages here.

en	Defines all the parameters for this item in the customer preferences. 'PasswordRegExp' allows to match passwords against a regular expression. Define the minimum number of characters using 'PasswordMinSize'. Define if at least 2 lowercase and 2 uppercase letter characters are needed by setting the appropriate option to '1'. 'PasswordMin2Characters' defines if the password needs to contain at least 2 letter characters (set to 0 or 1). 'PasswordNeedDigit' controls the need of at least 1 digit (set to 0 or 1 to control).

en	Defines all the parameters for this notification transport.

en	Defines an external link to the database of the customer (e.g. 'http://yourhost/customer.php?CID=[% Data.CustomerID %]' or '').

en	Defines an icon with link to the google map page of the current location in appointment edit screen.

en	Defines an overview module to show the address book view of a customer user list.

en	Defines available article actions for Chat articles.

en	Defines available article actions for Email articles.

en	Defines available article actions for Internal articles.

en	Defines available article actions for Phone articles.

en	Defines available article actions for invalid articles.

en	Defines available groups for the admin overview screen.

en	Defines default headers for outgoing emails.

en	Defines from which ticket attributes the agent can select the result order.

en	Defines groups for preferences items.

en	Defines how many deployments the system should keep.

en	Defines if a pre-sorting by priority should be done in the queue view.

en	Defines if a pre-sorting by priority should be done in the service view.

en	Defines if a ticket lock is required in the email outbound screen of the agent interface (if the ticket isn't locked yet, the ticket gets locked and the current agent will be set automatically as its owner).

en	Defines if a ticket lock is required in the email resend screen of the agent interface (if the ticket isn't locked yet, the ticket gets locked and the current agent will be set automatically as its owner).

en	Defines if a ticket lock is required in the ticket merge screen of a zoomed ticket in the agent interface (if the ticket isn't locked yet, the ticket gets locked and the current agent will be set automatically as its owner).

en	Defines if a ticket lock is required in the ticket phone inbound screen of the agent interface (if the ticket isn't locked yet, the ticket gets locked and the current agent will be set automatically as its owner).

en	Defines if agents should be allowed to login if they have no shared secret stored in their preferences and therefore are not using two-factor authentication.

en	Defines if customers should be allowed to login if they have no shared secret stored in their preferences and therefore are not using two-factor authentication.

en	Defines if the communication between this system and OTRS Group servers that provide cloud services is possible. If set to 'Disable cloud services', some functionality will be lost such as system registration, support data sending, upgrading to and use of OTRS Business Solution™, OTRS Verify™, OTRS News and product News dashboard widgets, among others.

en	Defines if the enhanced mode should be used (enables use of table, replace, subscript, superscript, paste from word, etc.).

en	Defines if the first article should be displayed as expanded, that is visible for the related customer. If nothing defined, latest article will be expanded.

en	Defines if the message in the email outbound screen of the agent interface is visible for the customer by default.

en	Defines if the message in the email resend screen of the agent interface is visible for the customer by default.

en	Defines if the message in the ticket compose screen of the agent interface is visible for the customer by default.

en	Defines if the message in the ticket forward screen of the agent interface is visible for the customer by default.

en	Defines if the note in the close ticket screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket bulk screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket free text screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket note screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket owner screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket pending screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket priority screen of the agent interface is visible for the customer by default.

en	Defines if the note in the ticket responsible screen of the agent interface is visible for the customer by default.

en	Defines if the previously valid token should be accepted for authentication. This is slightly less secure but gives users 30 seconds more time to enter their one-time password.

en	Defines if the values for filters should be retrieved from all available tickets. If enabled, only values which are actually used in any ticket will be available for filtering. Please note: The list of customers will always be retrieved like this.

en	Defines if time accounting is mandatory in the agent interface. If enabled, a note must be entered for all ticket actions (no matter if the note itself is configured as active or is originally mandatory for the individual ticket action screen).

en	Defines out of office message template. Two string parameters (%s) available: end date and number of days left.

en	Defines queues that's tickets are used for displaying as calendar events.

en	Defines the HTTP hostname for the support data collection with the public module 'PublicSupportDataCollector' (e.g. used from the OTRS Daemon).

en	Defines the PostMaster header to be used on the filter for keeping the current state of the ticket.

en	Defines the agent preferences key where the shared secret key is stored.

en	Defines the available steps in time selections. Select "Minute" to be able to select all minutes of one hour from 1-59. Select "30 Minutes" to only make full and half hours available.

en	Defines the body text for notification mails sent to agents, about new password.

en	Defines the body text for notification mails sent to agents, with token about new requested password.

en	Defines the body text for notification mails sent to customers, about new password.

en	Defines the body text for notification mails sent to customers, with token about new requested password.

en	Defines the config options for the autocompletion feature.

en	Defines the config parameters of this item, to be shown in the preferences view. 'PasswordRegExp' allows to match passwords against a regular expression. Define the minimum number of characters using 'PasswordMinSize'. Define if at least 2 lowercase and 2 uppercase letter characters are needed by setting the appropriate option to '1'. 'PasswordMin2Characters' defines if the password needs to contain at least 2 letter characters (set to 0 or 1). 'PasswordNeedDigit' controls the need of at least 1 digit (set to 0 or 1 to control). 'PasswordMaxLoginFailed' allows to set an agent to invalid-temporarily if max failed logins reached. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Defines the config parameters of this item, to be shown in the preferences view. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Defines the customer preferences key where the shared secret key is stored.

en	Defines the default agent name in the ticket zoom view of the customer interface.

en	Defines the default auto response type of the article for this operation.

en	Defines the default front-end (HTML) theme to be used by the agents and customers. If you like, you can add your own theme. Please refer the administrator manual located at https://doc.otrs.com/doc/.

en	Defines the default next state of a ticket, in the ticket bulk screen of the agent interface.

en	Defines the default note body text for phone tickets in the ticket phone inbound screen of the agent interface.

en	Defines the default queue for new tickets in the agent interface.

en	Defines the default sender type for phone tickets in the ticket phone inbound screen of the agent interface.

en	Defines the default shown ticket search attribute for ticket search screen (AllTickets/ArchivedTickets/NotArchivedTickets).

en	Defines the default sort criteria for all queues displayed in the queue view.

en	Defines the default sort criteria for all services displayed in the service view.

en	Defines the default sort order for all services in the service view, after priority sort.

en	Defines the default subject for phone tickets in the ticket phone inbound screen of the agent interface.

en	Defines the default the number of seconds (from current time) to re-schedule a generic interface failed task.

en	Defines the default ticket attribute for ticket sorting of the ticket search result of this operation.

en	Defines the default ticket order in the ticket search result of the this operation. Up: oldest on top. Down: latest on top.

en	Defines the default ticket type for new customer tickets in the customer interface.

en	Defines the default ticket type.

en	Defines the default value for the action parameter for the public frontend. The action parameter is used in the scripts of the system.

en	Defines the displayed style of the From field in notes that are visible for customers. A default agent name can be defined in Ticket::Frontend::CustomerTicketZoom###DefaultAgentName setting.

en	Defines the event object types that will be handled via AdminAppointmentNotificationEvent.

en	Defines the fall-back path to open fetchmail binary. Note: The name of the binary needs to be 'fetchmail', if it is different please use a symbolic link.

en	Defines the format of responses in the ticket compose screen of the agent interface ([% Data.OrigFrom | html %] is From 1:1, [% Data.OrigFromName | html %] is only realname of From).

en	Defines the groups every customer will be in (if CustomerGroupSupport is enabled and you don't want to manage every customer for these groups).

en	Defines the height for the rich text editor component for this screen. Enter number (pixels) or percent value (relative).

en	Defines the height for the rich text editor component. Enter number (pixels) or percent value (relative).

en	Defines the history comment for the ticket phone inbound screen action, which gets used for ticket history in the agent interface.

en	Defines the history comment for this operation, which gets used for ticket history in the agent interface.

en	Defines the history type for the ticket phone inbound screen action, which gets used for ticket history in the agent interface.

en	Defines the history type for this operation, which gets used for ticket history in the agent interface.

en	Defines the hours and week days of the indicated calendar, to count the working time.

en	Defines the list of online repositories. Another installations can be used as repository, for example: Key="http://example.com/otrs/public.pl?Action=PublicRepository;File=" and Content="Some Name".

en	Defines the list of params that can be passed to ticket search function.

en	Defines the list of possible next actions on an error screen, a full path is required, then is possible to add external links if needed.

en	Defines the list of types for templates.

en	Defines the maximum number of affected tickets per job.

en	Defines the maximum number of quoted lines to be added to responses.

en	Defines the maximum number of tasks to be executed as the same time.

en	Defines the maximum size in KiloByte of GenericInterface responses that get logged to the gi_debugger_entry_content table.

en	Defines the module that shows a generic notification in the agent interface. Either "Text" - if configured - or the contents of "File" will be displayed.

en	Defines the module that shows all the currently logged in customers in the agent interface.

en	Defines the module that shows the currently logged in agents in the customer interface.

en	Defines the module that shows the currently logged in customers in the customer interface.

en	Defines the module to display a notification if cloud services are disabled.

en	Defines the module to display a notification in the agent interface if the OTRS Daemon is not running.

en	Defines the module to display a notification in the agent interface if the system configuration is out of sync.

en	Defines the module to display a notification in the agent interface, if the agent has not yet selected a time zone.

en	Defines the module to display a notification in the agent interface, if the agent is logged in while having out-of-office active.

en	Defines the module to display a notification in the agent interface, if the agent is logged in while having system maintenance active.

en	Defines the module to display a notification in the agent interface, if the agent session limit prior warning is reached.

en	Defines the module to display a notification in the agent interface, if the installation of not verified packages is activated (only shown to admins).

en	Defines the module to display a notification in the agent interface, if there are invalid sysconfig settings deployed.

en	Defines the module to display a notification in the agent interface, if there are modified sysconfig settings that are not deployed yet.

en	Defines the module to display a notification in the customer interface, if the customer is logged in while having system maintenance active.

en	Defines the module to display a notification in the customer interface, if the customer user has not yet selected a time zone.

en	Defines the module to generate code for periodic page reloads.

en	Defines the module to send emails. "DoNotSendEmail" doesn't send emails at all. Any of the "SMTP" mechanisms use a specified (external) mailserver. "Sendmail" directly uses the sendmail binary of your operating system. "Test" doesn't send emails, but writes them to $OTRS_HOME/var/tmp/CacheFileStorable/EmailTest/ for testing purposes.

en	Defines the name of the table where the user preferences are stored.

en	Defines the next state of a ticket, in the ticket bulk screen of the agent interface.

en	Defines the number of character per line used in case an HTML article preview replacement on TemplateGenerator for EventNotifications.

en	Defines the number of days to keep the daemon log files.

en	Defines the number of header fields in frontend modules for add and update postmaster filters. It can be up to 99 fields.

en	Defines the number of hours a communication will be stored, whichever its status.

en	Defines the number of hours a successful communication will be stored.

en	Defines the parameters for the dashboard backend. "Cmd" is used to specify command with parameters. "Group" is used to restrict access to the plugin (e. g. Group: admin;group1;group2;). "Default" indicates if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTL" indicates the cache expiration period in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Defines the parameters for the dashboard backend. "Group" is used to restrict access to the plugin (e. g. Group: admin;group1;group2;). "Default" indicates if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTL" indicates the cache expiration period in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Defines the parameters for the dashboard backend. "Group" is used to restrict access to the plugin (e. g. Group: admin;group1;group2;). "Default" indicates if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" defines the cache expiration period in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Defines the parameters for the dashboard backend. "Limit" defines the number of entries displayed by default. "Group" is used to restrict access to the plugin (e. g. Group: admin;group1;group2;). "Default" indicates if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTL" indicates the cache expiration period in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Defines the parameters for the dashboard backend. "Limit" defines the number of entries displayed by default. "Group" is used to restrict access to the plugin (e. g. Group: admin;group1;group2;). "Default" indicates if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" defines the cache expiration period in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Defines the path of the shown info file, that is located under Kernel/Output/HTML/Templates/Standard/CustomerAccept.tt.

en	Defines the priority in which the information is logged and presented.

en	Defines the recipient target of the phone ticket and the sender of the email ticket ("Queue" shows all queues, "System address" displays all system addresses) in the agent interface.

en	Defines the recipient target of the tickets ("Queue" shows all queues, "SystemAddress" shows only the queues which are assigned to system addresses) in the customer interface.

en	Defines the required permission to show a ticket in the escalation view of the agent interface.

en	Defines the search parameters for the AgentCustomerUserAddressBook screen. With the setting 'CustomerTicketTextField' the values for the recipient field can be specified.

en	Defines the shown columns and the position in the AgentCustomerUserAddressBook result screen.

en	Defines the shown links in the footer area of the customer and public interface of this OTRS system. The value in "Key" is the external URL, the value in "Content" is the shown label.

en	Defines the ticket appointment type backend for ticket dynamic field date time.

en	Defines the ticket appointment type backend for ticket escalation time.

en	Defines the ticket appointment type backend for ticket pending time.

en	Defines the ticket fields that are going to be displayed calendar events. The "Key" defines the field or ticket attribute and the "Content" defines the display name.

en	Defines the time zone of the indicated calendar, which can be assigned later to a specific queue.

en	Defines the timeout (in seconds, minimum is 20 seconds) for the support data collection with the public module 'PublicSupportDataCollector' (e.g. used from the OTRS Daemon).

en	Defines the two-factor module to authenticate agents.

en	Defines the two-factor module to authenticate customers.

en	Defines the used character for plaintext email quotes in the ticket compose screen of the agent interface. If this is empty or inactive, original emails will not be quoted but appended to the response.

en	Defines the users avatar. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Defines the valid state types for a ticket. If a ticket is in a state which have any state type from this setting, this ticket will be considered as open, otherwise as closed.

en	Defines the valid states for unlocked tickets. To unlock tickets the script "bin/otrs.Console.pl Maint::Ticket::UnlockTimeout" can be used.

en	Defines the viewable locks of a ticket. NOTE: When you change this setting, make sure to delete the cache in order to use the new value. Default: unlock, tmp_lock.

en	Defines the width for the rich text editor component for this screen. Enter number (pixels) or percent value (relative).

en	Defines time in minutes since last modification for drafts of specified type before they are considered expired.

en	Defines whether to index archived tickets for fulltext searches.

en	Defines which article sender types should be shown in the preview of a ticket.

en	Defines which items are available for 'Action' in third level of the ACL structure.

en	Defines which items are available in first level of the ACL structure.

en	Defines which items are available in second level of the ACL structure.

en	Defines, which tickets of which ticket state types should not be listed in linked ticket lists.

en	Delete expired cache from core modules.

en	Delete expired loader cache weekly (Sunday mornings).

en	Delete expired upload cache hourly.

en	Delivers extended debugging information in the frontend in case any AJAX errors occur, if enabled.

en	Detached

en	Determines if a button to delete a link should be displayed next to each link in each zoom mask.

en	Determines the next possible ticket states, for process tickets in the agent interface.

en	Determines the next possible ticket states, for process tickets in the customer interface.

en	Determines the next screen after the ticket is moved. LastScreenOverview will return the last overview screen (e.g. search results, queueview, dashboard). TicketZoom will return to the TicketZoom.

en	Determines the strings that will be shown as recipient (To:) of the phone ticket and as sender (From:) of the email ticket in the agent interface. For Queue as NewQueueSelectionType "<Queue>" shows the names of the queues and for SystemAddress "<Realname> <<Email>>" shows the name and email of the recipient.

en	Determines the strings that will be shown as recipient (To:) of the ticket in the customer interface. For Queue as CustomerPanelSelectionType, "<Queue>" shows the names of the queues, and for SystemAddress, "<Realname> <<Email>>" shows the name and email of the recipient.

en	Determines which options will be valid of the recipient (phone ticket) and the sender (email ticket) in the agent interface.

en	Disable autocomplete in the login screen.

en	Disables the redirection to the last screen overview / dashboard after a ticket is closed.

en	Disables the web installer (http://yourhost.example.com/otrs/installer.pl), to prevent the system from being hijacked. If not enabled, the system can be reinstalled and the current basic configuration will be used to pre-populate the questions within the installer script. If enabled, it also disables the GenericAgent, PackageManager and SQL Box.

en	Display a warning and prevent search when using stop words within fulltext search.

en	Display settings to override defaults for Process Tickets.

en	Displays the number of all tickets with the same CustomerID as current ticket in the ticket zoom view.

en	Dutch

en	Dutch stop words for fulltext index. These words will be removed from the search index.

en	Dynamic fields groups for process widget. The key is the name of the group, the value contains the fields to be shown. Example: 'Key => My Group', 'Content: Name_X, NameY'.

en	Dynamic fields options shown in the ticket message screen of the customer interface. NOTE. If you want to display these fields also in the ticket zoom of the customer interface, you have to enable them in CustomerTicketZoom###DynamicField.

en	Dynamic fields options shown in the ticket reply section in the ticket zoom screen of the customer interface.

en	Dynamic fields shown in the ticket medium format overview screen of the agent interface.

en	Dynamic fields shown in the ticket overview screen of the customer interface.

en	Dynamic fields shown in the ticket owner screen of the agent interface.

en	Dynamic fields shown in the ticket pending screen of the agent interface.

en	Dynamic fields shown in the ticket phone inbound screen of the agent interface.

en	Dynamic fields shown in the ticket phone outbound screen of the agent interface.

en	Dynamic fields shown in the ticket phone screen of the agent interface.

en	Dynamic fields shown in the ticket print screen of the customer interface.

en	Dynamic fields shown in the ticket search overview results screen of the customer interface.

en	Dynamic fields shown in the ticket search screen of the customer interface.

en	Dynamic fields shown in the ticket zoom screen of the customer interface.

en	Enable highlighting queues based on ticket age.

en	Enable keep-alive connection header for SOAP responses.

en	Enable this if you trust in all your public and private pgp keys, even if they are not certified with a trusted signature.

en	Enables or disables the caching for templates. WARNING: Do NOT disable template caching for production environments for it will cause a massive performance drop! This setting should only be disabled for debugging reasons!

en	Enables or disables the debug mode over frontend interface.

en	Enables the minimal ticket counter size (if "Date" was selected as TicketNumberGenerator).

en	Enables ticket type feature.

en	English stop words for fulltext index. These words will be removed from the search index.

en	Enroll process for this ticket

en	Enter your shared secret to enable two factor authentication. WARNING: Make sure that you add the shared secret to your generator application and the application works well. Otherwise you will be not able to login anymore without the two factor token.

en	EscalationTime

en	Event module registration. For more performance you can define a trigger event (e. g. Event => TicketCreate).

en	Event module registration. For more performance you can define a trigger event (e. g. Event => TicketCreate). This is only possible if all Ticket dynamic fields need the same event.

en	Event module that performs an update statement on TicketIndex to rename the queue name there if needed and if StaticDB is actually used.

en	Event module that updates customer company object name for dynamic fields.

en	Executes a custom command or module. Note: if module is used, function is required.

en	Executes follow-up checks on In-Reply-To or References headers for mails that don't have a ticket number in the subject.

en	Executes follow-up checks on OTRS Header 'X-OTRS-Bounce'.

en	Executes follow-up checks on attachment contents for mails that don't have a ticket number in the subject.

en	Executes follow-up checks on email body for mails that don't have a ticket number in the subject.

en	Executes follow-up checks on the raw source email for mails that don't have a ticket number in the subject.

en	Fetch emails via fetchmail (using SSL).

en	Fetch emails via fetchmail.

en	Fetch incoming emails from configured mail accounts.

en	File that is displayed in the Kernel::Modules::AgentInfo module, if located under Kernel/Output/HTML/Templates/Standard/AgentInfo.tt.

en	Filter for debugging ACLs. Note: More ticket attributes can be added in the format <OTRS_TICKET_Attribute> e.g. <OTRS_TICKET_Priority>.

en	Filter for debugging Transitions. Note: More filters can be added in the format <OTRS_TICKET_Attribute> e.g. <OTRS_TICKET_Priority>.

en	For these state types the ticket numbers are striked through in the link table.

en	Force the storage of the original article text in the article search index, without executing filters or applying stop word lists. This will increase the size of the search index and thus may slow down fulltext searches.

en	French stop words for fulltext index. These words will be removed from the search index.

en	Full value

en	Fulltext index regex filters to remove parts of the text.

en	General ticket data shown in the ticket overviews (fall-back). Note that TicketNumber can not be disabled, because it is necessary.

en	Generic Info module.

en	GenericInterface module registration for an error handling module.

en	GenericInterface module registration for the invoker layer.

en	GenericInterface module registration for the mapping layer.

en	GenericInterface module registration for the operation layer.

en	GenericInterface module registration for the transport layer.

en	German stop words for fulltext index. These words will be removed from the search index.

en	Gives customer users group based access to tickets from customer users of the same customer (ticket CustomerID is a CustomerID of the customer user).

en	Gives end users the possibility to override the separator character for CSV files, defined in the translation files. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Global Search Module.

en	Good PGP signature.
ja	署名を追加

en	Google Authenticator

en	Helps to extend your articles full-text search (From, To, Cc, Subject and Body search). It will strip all articles and will build an index after article creation, increasing fulltext searches about 50%. To create an initial index use "bin/otrs.Console.pl Maint::Ticket::FulltextIndex --rebuild".

en	High Contrast

en	High contrast skin for visually impaired users.

en	If "DB" was selected for Customer::AuthModule, the encryption type of passwords must be specified.

en	If "HTTPBasicAuth" was selected for Customer::AuthModule, you can specify to strip leading parts of user names (e. g. for domains like example_domain\\user to user).

en	If "bcrypt" was selected for CryptType, use cost specified here for bcrypt hashing. Currently max. supported cost value is 31.

en	If active, none of the regular expressions may match the user's email address to allow registration.

en	If active, one of the regular expressions has to match the user's email address to allow registration.

en	If enabled debugging information for ACLs is logged.

en	If enabled debugging information for transitions is logged.

en	If enabled the daemon will redirect the standard error stream to a log file.

en	If enabled the daemon will redirect the standard output stream to a log file.

en	If enabled the daemon will use this directory to create its PID files. Note: Please stop the daemon before any change and use this setting only if <$OTRSHome>/var/run/ can not be used.

en	If enabled, OTRS will deliver all CSS files in minified form.

en	If enabled, the OTRS version tag will be removed from the Webinterface, the HTTP headers and the X-Headers of outgoing mails. NOTE: If you change this option, please make sure to delete the cache.

en	If enabled, the cache data be held in memory.

en	If enabled, the cache data will be stored in cache backend.

en	If enabled, the customer can search for tickets in all services (regardless what services are assigned to the customer).

en	If enabled, users that haven't selected a time zone yet will be notified to do so. Note: Notification will not be shown if (1) user has not yet selected a time zone and (2) OTRSTimeZone and UserDefaultTimeZone do match and (3) are not set to UTC.

en	If no SendmailNotificationEnvelopeFrom is specified, this setting makes it possible to use the email's from address instead of an empty envelope sender (required in certain mail server configurations).

en	If set, this address is used as envelope sender header in outgoing notifications. If no address is specified, the envelope sender header is empty (unless SendmailNotificationEnvelopeFrom::FallbackToEmailFrom is set).

en	If set, this address is used as envelope sender in outgoing messages (not notifications - see below). If no address is specified, the envelope sender is equal to queue e-mail address.

en	If this option is enabled, tickets created via the web interface, via Customers or Agents, will receive an autoresponse if configured. If this option is not enabled, no autoresponses will be sent.

en	If this setting is enabled, it is possible to install packages which are not verified by OTRS Group. These packages could threaten your whole system!

en	If this setting is enabled, local modifications will not be highlighted as errors in the package manager and support data collector.

en	Ignore system sender article types (e. g. auto responses or email notifications) to be flagged as 'Unread Article' in AgentTicketZoom or expanded automatically in Large view screens.

en	Include tickets of subqueues per default when selecting a queue.

en	Include unknown customers in ticket filter.

en	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.

en	Indicates if a bounce e-mail should always be treated as normal follow-up.

en	Indonesian

en	Inline

en	It was not possible to check the PGP signature, this may be caused by a missing public key or an unsupported algorithm.

en	Italian stop words for fulltext index. These words will be removed from the search index.

en	Ivory

en	Ivory (Slim)

en	JavaScript function for the search frontend.

en	Korean

en	Last Screen Overview

en	Last customer subject

en	Lastname Firstname

en	Lastname Firstname (UserLogin)

en	LastnameFirstname

en	Link templates to attachments.

en	Links appointments and tickets with a "Normal" type link.

en	List of all CustomerCompany events to be displayed in the GUI.

en	List of all CustomerUser events to be displayed in the GUI.

en	List of all DynamicField events to be displayed in the GUI.

en	List of all LinkObject events to be displayed in the GUI.

en	List of all Package events to be displayed in the GUI.

en	List of all appointment events to be displayed in the GUI.

en	List of all article events to be displayed in the GUI.

en	List of all calendar events to be displayed in the GUI.

en	List of all queue events to be displayed in the GUI.

en	List of all ticket events to be displayed in the GUI.

en	List of colors in hexadecimal RGB which will be available for selection during calendar creation. Make sure the colors are dark enough so white text can be overlayed on them.

en	List of responsive CSS files to always be loaded for the agent interface.

en	List of responsive CSS files to always be loaded for the customer interface.

en	Loader module registration for the customer interface.

en	Macedonian

en	Main menu item registration.

en	Main menu registration.

en	Makes the application block external content loading.

en	Max size (in characters) of the customer information table (phone and email) in the compose screen.

en	Max size (in rows) of the informed agents box in the agent interface.

en	Max size (in rows) of the involved agents box in the agent interface.

en	Max size of the subjects in an email reply and in some overview screens.

en	Maximal auto email responses to own email-address a day, configurable by email address (Loop-Protection).

en	Maximum Number of a calendar shown in a dropdown.

en	Maximum length (in characters) of the dynamic field in the article of the ticket zoom view.

en	Maximum length (in characters) of the dynamic field in the sidebar of the ticket zoom view.

en	Maximum number of active calendars in overview screens. Please note that large number of active calendars can have a performance impact on your server by making too much simultaneous calls.

en	Maximum number of tickets to be displayed in the result of this operation.

en	Module to check if a incoming e-mail message is bounce.

en	Module to check if arrived emails should be marked as internal (because of original forwarded internal email). IsVisibleForCustomer and SenderType define the values for the arrived email/article.

en	Module to encrypt composed messages (PGP or S/MIME).

en	Module to fetch customer users SMIME certificates of incoming messages.

en	Module to filter encrypted bodies of incoming messages.

en	Module to grant access if the CustomerID of the customer has necessary group permissions.

en	Module to grant access if the CustomerID of the ticket matches the CustomerID of the customer.

en	Module to grant access if the CustomerUserID of the ticket matches the CustomerUserID of the customer.

en	Module to grant access to any agent that has been involved in a ticket in the past (based on ticket history entries).

en	Module to grant access to the agent responsible of a ticket.

en	Module to grant access to the creator of a ticket.

en	Module to grant access to the owner of a ticket.

en	Module to grant access to the watcher agents of a ticket.

en	Module used to detect if attachments are present.

en	Name of custom service. The custom service is a service selection of your preferred services and can be selected in the preferences settings.

en	NameX

en	News about OTRS.

en	Next possible ticket states after adding a phone note in the ticket phone inbound screen of the agent interface.

en	No public key found.
ja	チケットデータがありません

en	No valid OpenPGP data found.
ja	チケットデータがありません

en	Number of tickets to be displayed in each page.

en	OTRS doesn't support recurring Appointments without end date or number of iterations. During import process, it might happen that ICS file contains such Appointments. Instead, system creates all Appointments in the past, plus Appointments for the next N months (120 months/10 years by default).

en	Optional queue limitation for the CreatorCheck permission module. If set, permission is only granted for tickets in the specified queues.

en	Optional queue limitation for the InvolvedCheck permission module. If set, permission is only granted for tickets in the specified queues.

en	Optional queue limitation for the OwnerCheck permission module. If set, permission is only granted for tickets in the specified queues.

en	Optional queue limitation for the ResponsibleCheck permission module. If set, permission is only granted for tickets in the specified queues.

en	Other Customers

en	Out of Office users.

en	Package event module file a scheduler task for update registration.

en	Parameters for the CreateNextMask object in the preference view of the agent interface. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the CustomQueue object in the preference view of the agent interface. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the CustomService object in the preference view of the agent interface. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the RefreshTime object in the preference view of the agent interface. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the column filters of the small ticket overview. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the dashboard backend of the customer company information of the agent interface. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin.

en	Parameters for the dashboard backend of the customer id list overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin.

en	Parameters for the dashboard backend of the customer id status widget of the agent interface . "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin.

en	Parameters for the dashboard backend of the customer user information of the agent interface. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin.

en	Parameters for the dashboard backend of the customer user list overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin.

en	Parameters for the dashboard backend of the new tickets overview of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the new tickets overview of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the open tickets overview of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the open tickets overview of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the queue overview widget of the agent interface. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "QueuePermissionGroup" is not mandatory, queues are only listed if they belong to this permission group if you enable it. "States" is a list of states, the key is the sort order of the state in the widget. "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Parameters for the dashboard backend of the running process tickets overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Parameters for the dashboard backend of the ticket escalation overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the ticket escalation overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the ticket escalation overview of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the ticket events calendar of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Parameters for the dashboard backend of the ticket pending reminder overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the ticket pending reminder overview of the agent interface . "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the ticket pending reminder overview of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. Note: Only Ticket attributes and Dynamic Fields (DynamicField_NameX) are allowed for DefaultColumns.

en	Parameters for the dashboard backend of the ticket stats of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Parameters for the dashboard backend of the upcoming events widget of the agent interface. "Limit" is the number of entries shown by default. "Group" is used to restrict the access to the plugin (e. g. Group: admin;group1;group2;). "Default" determines if the plugin is enabled by default or if the user needs to enable it manually. "CacheTTLLocal" is the cache time in minutes for the plugin. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Parameters for the pages (in which the communication log entries are shown) of the communication log overview.

en	Parameters for the pages (in which the dynamic fields are shown) of the dynamic fields overview. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the pages (in which the tickets are shown) of the medium ticket overview. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the pages (in which the tickets are shown) of the small ticket overview. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Parameters for the pages (in which the tickets are shown) of the ticket preview overview. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Performs the configured action for each event (as an Invoker) for each configured web service.

en	Phone Call.

en	Picture upload module.

en	Protection against CSRF (Cross Site Request Forgery) exploits (for more info see https://en.wikipedia.org/wiki/Cross-site_request_forgery).

en	Provides customer users access to tickets even if the tickets are not assigned to a customer user of the same customer ID(s), based on permission groups.

en	Queues ↔ Auto Responses

en	Recognize if a ticket is a follow-up to an existing ticket using an external ticket number. Note: the first capturing group from the 'NumberRegExp' expression will be used as the ticket number value.

en	Registers a log module, that can be used to log communication related information.

en	Removes old generic interface debug log entries created before the specified amount of days.

en	Removes old ticket number counters (each 10 minutes).

en	Renew existing SMIME certificates from customer backend. Note: SMIME and SMIME::FetchFromCustomer needs to be enabled in SysConfig and customer backend needs to be configured to fetch UserSMIMECertificate attribute.

en	Reprocess mails from spool directory that could not be imported in the first place.

en	Required permissions to use the email outbound screen in the agent interface.

en	Required permissions to use the email resend screen in the agent interface.

en	Required permissions to use the ticket phone inbound screen in the agent interface.

en	Resent email to "%s".

en	Responsible Tickets

en	Responsible Tickets.

en	Restores a ticket from the archive (only if the event is a state change to any open available state).

en	Retains all services in listings even if they are children of invalid elements.

en	Romanian

en	Run file based generic agent jobs (Note: module name needs to be specified in -configuration-module param e.g. "Kernel::System::GenericAgent").

en	Runs an initial wildcard search of the existing customer company when accessing the AdminCustomerCompany module.

en	Runs the system in "Demo" mode. If enabled, agents can change preferences, such as selection of language and theme via the agent web interface. These changes are only valid for the current session. It will not be possible for agents to change their passwords.

en	Sample command output

en	Saves the attachments of articles. "DB" stores all data in the database (not recommended for storing big attachments). "FS" stores the data on the filesystem; this is faster but the webserver should run under the OTRS user. You can switch between the modules even on a system that is already in production without any loss of data. Note: Searching for attachment names is not supported when "FS" is used.

en	Select your preferred theme for OTRS.

en	Selects the ticket number generator module. "AutoIncrement" increments the ticket number, the SystemID and the counter are used with SystemID.counter format (e.g. 1010138, 1010139). With "Date" the ticket numbers will be generated by the current date, the SystemID and the counter. The format looks like Year.Month.Day.SystemID.counter (e.g. 200206231010138, 200206231010139). With "DateChecksum" the counter will be appended as checksum to the string of date and SystemID. The checksum will be rotated on a daily basis. The format looks like Year.Month.Day.SystemID.Counter.CheckSum (e.g. 2002070110101520, 2002070110101535).

en	Sends customer notifications just to the mapped customer.

en	Sends registration information to OTRS group.

en	Sends the notifications which are configured in the admin interface under "Ticket Notifications".

en	Sent "%s" notification to "%s" via "%s".

en	Set the limit of tickets that will be executed on a single genericagent job execution.

en	Set the minimum log level. If you select 'error', just errors are logged. With 'debug' you get all logging messages. The order of log levels is: 'debug', 'info', 'notice' and 'error'.

en	Sets if note must be filled in by the agent. Can be overwritten by Ticket::Frontend::NeedAccountedTime.

en	Sets if state must be selected by the agent.

en	Sets if ticket responsible must be selected by the agent.

en	Sets the count of articles visible in preview mode of ticket overviews.

en	Sets the default error message for the login screen on Agent and Customer interface, it's shown when a running system maintenance period is active.

en	Sets the default message for the login screen on Agent and Customer interface, it's shown when a running system maintenance period is active.

en	Sets the default message for the notification is shown on a running system maintenance period.

en	Sets the inactivity time (in seconds) to pass before a session is killed and a user is logged out.

en	Sets the maximum number of active agents within the timespan defined in SessionMaxIdleTime before a prior warning will be visible for the logged in agents.

en	Sets the maximum number of active agents within the timespan defined in SessionMaxIdleTime.

en	Sets the maximum number of active customers within the timespan defined in SessionMaxIdleTime.

en	Sets the maximum number of active sessions per agent within the timespan defined in SessionMaxIdleTime.

en	Sets the maximum number of active sessions per customers within the timespan defined in SessionMaxIdleTime.

en	Sets the method PGP will use to sing and encrypt emails. Note Inline method is not compatible with RichText messages.

en	Sets the minimal ticket counter size if "AutoIncrement" was selected as TicketNumberGenerator. Default is 5, this means the counter starts from 10000.

en	Sets the minutes a notification is shown for notice about upcoming system maintenance period.

en	Sets the preferred digest to be used for PGP binary.

en	Sets the service in the close ticket screen of the agent interface (Ticket::Service needs to be enabled).

en	Sets the service in the ticket free text screen of the agent interface (Ticket::Service needs to be enabled).

en	Sets the service in the ticket note screen of the agent interface (Ticket::Service needs to be enabled).

en	Sets the service in the ticket owner screen of a zoomed ticket in the agent interface (Ticket::Service needs to be enabled).

en	Sets the service in the ticket pending screen of a zoomed ticket in the agent interface (Ticket::Service needs to be enabled).

en	Sets the service in the ticket priority screen of a zoomed ticket in the agent interface (Ticket::Service needs to be enabled).

en	Sets the service in the ticket responsible screen of the agent interface (Ticket::Service needs to be enabled).

en	Sets the state of a ticket in the close ticket screen of the agent interface.

en	Sets the state of a ticket in the ticket bulk screen of the agent interface.

en	Sets the state of a ticket in the ticket free text screen of the agent interface.

en	Sets the state of a ticket in the ticket note screen of the agent interface.

en	Sets the state of a ticket in the ticket responsible screen of the agent interface.

en	Sets the state of the ticket in the ticket owner screen of a zoomed ticket in the agent interface.

en	Sets the state of the ticket in the ticket pending screen of a zoomed ticket in the agent interface.

en	Sets the state of the ticket in the ticket priority screen of a zoomed ticket in the agent interface.

en	Sets the ticket type in the close ticket screen of the agent interface (Ticket::Type needs to be enabled).

en	Sets the ticket type in the ticket bulk screen of the agent interface.

en	Sets the ticket type in the ticket free text screen of the agent interface (Ticket::Type needs to be enabled).

en	Sets the ticket type in the ticket note screen of the agent interface (Ticket::Type needs to be enabled).

en	Sets the ticket type in the ticket owner screen of a zoomed ticket in the agent interface (Ticket::Type needs to be enabled).

en	Sets the ticket type in the ticket pending screen of a zoomed ticket in the agent interface (Ticket::Type needs to be enabled).

en	Sets the ticket type in the ticket priority screen of a zoomed ticket in the agent interface (Ticket::Type needs to be enabled).

en	Sets the ticket type in the ticket responsible screen of the agent interface (Ticket::Type needs to be enabled).

en	Sets the time zone being used internally by OTRS to e. g. store dates and times in the database. WARNING: This setting must not be changed once set and tickets or any other data containing date/time have been created.

en	Sets the time zone that will be assigned to newly created users and will be used for users that haven't yet set a time zone. This is the time zone being used as default to convert date and time between the OTRS time zone and the user's time zone.

en	Shared Secret

en	Show command line output.

en	Show queues even when only locked tickets are in.

en	Show the current owner in the customer interface.

en	Show the current queue in the customer interface.

en	Shows a count of attachments in the ticket zoom, if the article has attachments.

en	Shows a link in the menu for creating a calendar appointment linked to the ticket directly from the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu for subscribing / unsubscribing from a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu that allows linking a ticket with another object in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu that allows merging tickets in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to access the history of a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to add a free text field in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to add a note in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to add a phone call inbound in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to add a phone call outbound in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to change the customer who requested the ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to change the owner of a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to change the responsible agent of a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to close a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to delete a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to enroll a ticket into a process in the ticket zoom view of the agent interface.

en	Shows a link in the menu to go back in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to lock/unlock tickets in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to print a ticket or an article in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to see the priority of a ticket in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to send an outbound email in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link in the menu to set a ticket as junk in every ticket overview of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Shows a link in the menu to set a ticket as pending in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a link to set a ticket as junk in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2". To cluster menu items use for Key "ClusterName" and for the Content any name you want to see in the UI. Use "ClusterPriority" to configure the order of a certain cluster within the toolbar.

en	Shows a teaser link in the menu for the ticket attachment view of OTRS Business Solution™.

en	Shows all the articles of the ticket (expanded) in the agent zoom view.

en	Shows all the articles of the ticket (expanded) in the customer zoom view.

en	Shows all the customer user identifiers in a multi-select field (not useful if you have a lot of customer user identifiers).

en	Shows link to external page in the ticket zoom view of the agent interface. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Shows the article head information in the agent zoom view.

en	Shows the enabled ticket attributes in the customer interface (0 = Disabled and 1 = Enabled).

en	Shows the message of the day (MOTD) in the agent dashboard. "Group" is used to restrict access to the plugin (e. g. Group: admin;group1;group2;). "Default" indicates if the plugin is enabled by default or if the user needs to enable it manually. "Mandatory" determines if the plugin is always shown and can not be removed by agents.

en	Shows the title field in the close ticket screen of the agent interface.

en	Shows the title field in the ticket free text screen of the agent interface.

en	Shows the title field in the ticket note screen of the agent interface.

en	Shows the title field in the ticket owner screen of a zoomed ticket in the agent interface.

en	Shows the title field in the ticket pending screen of a zoomed ticket in the agent interface.

en	Shows the title field in the ticket priority screen of a zoomed ticket in the agent interface.

en	Shows the title field in the ticket responsible screen of the agent interface.

en	Shows time in long format (days, hours, minutes), if enabled; or in short format (days, hours), if not enabled.

en	Shows time use complete description (days, hours, minutes), if enabled; or just first letter (d, h, m), if not enabled.

en	Signature data.
ja	署名を更新しました。

en	Sorts the tickets (ascendingly or descendingly) when a single queue is selected in the service view and after the tickets are sorted by priority. Values: 0 = ascending (oldest on top, default), 1 = descending (youngest on top). Use the ServiceID for the key and 0 or 1 for value.

en	Spanish stop words for fulltext index. These words will be removed from the search index.

en	Specifies the directory to store the data in, if "FS" was selected for ArticleStorage.

en	Specifies the email address that should be used by the application when sending notifications. The email address is used to build the complete display name for the notification master (i.e. "OTRS Notifications" otrs@your.example.com). You can use the OTRS_CONFIG_FQDN variable as set in your configuation, or choose another email address.

en	Specifies the email addresses to get notification messages from scheduler tasks.

en	Specifies the group where the user needs rw permissions so that they can edit other users preferences.

en	Specifies the name that should be used by the application when sending notifications. The sender name is used to build the complete display name for the notification master (i.e. "OTRS Notifications" otrs@your.example.com).

en	Specifies whether all storage backends should be checked when looking for attachments. This is only required for installations where some attachments are in the file system, and others in the database.

en	Specifies whether the (MIMEBase) article attachments will be indexed and searchable.

en	Specify how many sub directory levels to use when creating cache files. This should prevent too many cache files being in one directory.

en	Specify the channel to be used to fetch OTRS Business Solution™ updates. Warning: Development releases might not be complete, your system might experience unrecoverable errors and on extreme cases could become unresponsive!

en	Specify the username to authenticate for the first mirror database.

en	Starts a wildcard search of the active object after the link object mask is started.

en	Statistic Reports overview.

en	Strips empty lines on the ticket preview in the service view.

en	Support Agent

en	Templates ↔ Attachments

en	The PGP signature is expired.
ja	メール回答の署名

en	The PGP signature was made by a revoked key, this could mean that the signature is forged.

en	The PGP signature was made by an expired key.

en	The PGP signature with the keyid has not been verified successfully.

en	The PGP signature with the keyid is good.

en	The daemon registration for the scheduler cron task manager.

en	The daemon registration for the scheduler future task manager.

en	The daemon registration for the scheduler generic agent task manager.

en	The daemon registration for the scheduler task worker.

en	The daemon registration for the system configuration deployment sync manager.

en	The duration in minutes after emitting an event, in which the new escalation notify and start events are suppressed.

en	The format of the subject. 'Left' means '[TicketHook#:12345] Some Subject', 'Right' means 'Some Subject [TicketHook#:12345]', 'None' means 'Some Subject' and no ticket number. In the latter case you should verify that the setting PostMaster::CheckFollowUpModule###0200-References is activated to recognize followups based on email headers.

en	The logo shown in the header of the agent interface for the skin "High Contrast". See "AgentLogo" for further description.

en	The logo shown in the header of the agent interface. The URL to the image can be a relative URL to the skin image directory, or a full URL to a remote web server.

en	The logo shown on top of the login box of the agent interface. The URL to the image can be a relative URL to the skin image directory, or a full URL to a remote web server.

en	The secret you supplied is invalid. The secret must only contain letters (A-Z, uppercase) and numbers (2-7) and must consist of 16 characters.

en	The value of the From field

en	This event module stores attributes from CustomerUser as DynamicFields tickets. Please see DynamicFieldFromCustomerUser::Mapping setting for how to configure the mapping.

en	This is a Description for Comment on Framework.

en	This is a Description for DynamicField on Framework.

en	This key is not certified with a trusted signature!

en	This option will deny the access to customer company tickets, which are not created by the customer user.

en	This setting allows you to override the built-in country list with your own list of countries. This is particularly handy if you just want to use a small select group of countries.

en	This setting is deprecated. Set OTRSTimeZone instead.

en	This setting shows the sorting attributes in all overview screen, not only in queue view.

en	Ticket Compose email Answer.

en	Ticket event module that triggers the escalation stop events.

en	Ticket limit per page for Ticket Overview "Medium".

en	Ticket limit per page for Ticket Overview "Preview".

en	Ticket limit per page for Ticket Overview "Small".

en	To accept login information, such as an EULA or license.

en	Toggles display of OTRS FeatureAddons list in PackageManager.

en	Toolbar Item for a shortcut. Additional access control to show or not show this link can be done by using Key "Group" and Content like "rw:group1;move_into:group2".

en	Transport selection for appointment notifications. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Transport selection for ticket notifications. Please note: setting 'Active' to 0 will only prevent agents from editing settings of this group in their personal preferences, but will still allow administrators to edit the settings of another user's behalf. Use 'PreferenceGroup' to control in which area these settings should be shown in the user interface.

en	Triggers add or update of automatic calendar appointments based on certain ticket times.

en	Triggers ticket escalation events and notification events for escalation.

en	Turns on the remote ip address check. It should not be enabled if the application is used, for example, via a proxy farm or a dialup connection, because the remote ip address is mostly different for the requests.

en	Type of daemon log rotation to use: Choose 'OTRS' to let OTRS system to handle the file rotation, or choose 'External' to use a 3rd party rotation mechanism (i.e. logrotate). Note: External rotation mechanism requires its own and independent configuration.

en	Use new type of select and autocomplete fields in agent interface, where applicable (InputFields).

en	Use new type of select and autocomplete fields in customer interface, where applicable (InputFields).

en	Whether or not to collect meta information from articles using filters configured in Ticket::Frontend::ZoomCollectMetaFilters.

en	Whether to force redirect all requests from http to https protocol. Please check that your web server is configured correctly for https protocol before enable this option.