en	Add dynamic field

en	Last close times
pt-br	Última alteração

en	No last close time settings.
pt-br	Ignorar horários de fechamento

en	Ticket last close
pt-br	Chamado fechado

en	Ticket last close between
pt-br	Chamado fechado entre

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

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

en	Downgrade to ((OTRS)) Community Edition

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	You are about to downgrade to ((OTRS)) Community Edition and will lose the following features and all data related to these:

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

en	Detail View for SessionID: %s - %s

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

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	If you decide to downgrade to ((OTRS)) Community Edition, you will lose all database tables and data related to %s.

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

en	Fulltext Search in Tickets (e. g. "John*n" or "Will*")

en	Ticket Archive System

en	Save Search as Template?

en	Notifications (OTRS Business Solution™)

en	Could not get backend for Invoker %s

en	Regexp

en	Simple Mapping for Outgoing Data

en	Simple Mapping for Incoming Data

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	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	Article subject will be empty if the subject contains only the ticket hook!

en	HTML body attachment is missing!

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

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

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	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	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	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 following sequences with possible wrong names have been found. Please rename them manually.

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	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	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	Apache2::DBI Usage

en	Apache2::DBI should be used to get a better performance with pre-established database connections.

en	Added via Customer Panel (%s)

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

en	Follow-ups for closed tickets are not possible. A new ticket will be 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 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	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	Remove this dynamic field

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

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	Namespace %s could not be initialized, because %s could not be found.

en	Open this node in a new window

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

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

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	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	AgentTicketZoom widget that displays a table of objects linked to the ticket.

en	AgentTicketZoom widget that displays customer information for the ticket in the side bar.

en	AgentTicketZoom widget that displays ticket data in the side bar.

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 generic agent to execute custom command line scripts.

en	Allows generic agent to execute custom modules.

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

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

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.
pt-br	Verifica se o e-mail é uma continuação de um ticket existente ao pesquisar no assunto por um número de ticket válido.

en	Checks the availability of OTRS Business Solution™ for this system.

en	Checks the entitlement status of OTRS Business Solution™.

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	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 Ticket Print Module.

en	Customer preferences.

en	Customer ticket overview

en	Customer ticket search.

en	Customer ticket zoom

en	CustomerID search

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

en	Default agent name

en	Default display type for recipient (To,Cc) names in AgentTicketZoom and CustomerTicketZoom.

en	Default display type for sender (From) names in AgentTicketZoom and CustomerTicketZoom.

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	Defines if the enhanced mode should be used (enables use of table, replace, subscript, superscript, paste from word, etc.) in customer interface.

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

en	Defines if time accounting must be set to all tickets in bulk action.

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

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 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 customers, about new password.

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

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

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 for a ticket after customer follow-up in the customer interface.

en	Defines the default next state of a ticket after adding a note, in the ticket owner screen of a zoomed ticket in the agent interface.

en	Defines the default next state of a ticket after adding a note, in the ticket pending screen of a zoomed ticket in the agent interface.

en	Defines the default next state of a ticket after adding a note, in the ticket priority screen of a zoomed ticket in the agent interface.

en	Defines the default next state of a ticket after being bounced, in the ticket bounce screen of the agent interface.

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

en	Defines the default priority of follow-up customer tickets in the ticket zoom screen in the customer interface.

en	Defines the default sender type for tickets in the ticket zoom screen of the customer interface.

en	Defines the default ticket attribute for ticket sorting in a ticket search of the customer interface.

en	Defines the default ticket bounced notification for customer/sender in the ticket bounce screen of the agent interface.

en	Defines the default ticket order of a search result in the customer interface. Up: oldest on top. Down: latest on top.

en	Defines the default ticket priority in the ticket bulk screen of the agent interface.

en	Defines the default ticket priority in the ticket owner screen of a zoomed ticket in the agent interface.

en	Defines the default ticket priority in the ticket pending screen of a zoomed ticket in the agent interface.

en	Defines the default ticket priority in the ticket priority screen of a zoomed ticket in the agent interface.

en	Defines the default used Frontend-Module if no Action parameter given in the url on the customer interface.

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 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 history comment for the ticket zoom action, which gets used for ticket history in the customer interface.

en	Defines the history type for the ticket zoom action, which gets used for ticket history in the customer interface.

en	Defines the key to check with CustomerAccept. If this user preferences key is true, then the message is accepted by the system.

en	Defines the log module for the system. "File" writes all messages in a given logfile, "SysLog" uses the syslog daemon of the system, e.g. syslogd.

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 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 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 in different interfaces on different occasions for OTRS Business Solution™.

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 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 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 key for customer sessions.

en	Defines the next possible states for customer tickets in the customer interface.

en	Defines the next state of a ticket after adding a note, in the ticket free text screen of the agent interface.

en	Defines the next state of a ticket after adding a note, in the ticket owner screen of a zoomed ticket in the agent interface.

en	Defines the next state of a ticket after adding a note, in the ticket pending screen of a zoomed ticket in the agent interface.

en	Defines the next state of a ticket after adding a note, in the ticket priority screen of a zoomed ticket in the agent interface.

en	Defines the next state of a ticket after being bounced, in the ticket bounce screen of the agent interface.

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 password to access the SOAP handle (bin/cgi-bin/rpc.pl).

en	Defines the path and TTF-File to handle bold italic monospaced font in PDF documents.

en	Defines the path and TTF-File to handle bold italic proportional font in PDF documents.

en	Defines the path and TTF-File to handle bold monospaced font in PDF documents.

en	Defines the path and TTF-File to handle bold proportional font in PDF documents.

en	Defines the path and TTF-File to handle italic monospaced font in PDF documents.

en	Defines the path and TTF-File to handle italic proportional font in PDF documents.

en	Defines the path and TTF-File to handle monospaced font in PDF documents.

en	Defines the path and TTF-File to handle proportional font in PDF documents.

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

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 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 subject for notification mails sent to customers, about new password.

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

en	Defines the system identifier. Every ticket number and http session string contains this ID. This ensures that only tickets which belong to your system will be processed as follow-ups (useful when communicating between two instances of OTRS).

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 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 user identifier for the customer panel.

en	Defines the username to access the SOAP handle (bin/cgi-bin/rpc.pl).

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 width for the rich text editor component for this screen. Enter number (pixels) or percent value (relative).

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

en	Defines whether to index archived tickets for fulltext searches.

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

en	Determines the next screen after the follow-up screen of a zoomed ticket in the customer interface.

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 queues will be valid for ticket's recepients in the customer interface.

en	Disable autocomplete in the login screen.

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	Dutch stop words for fulltext index. These words will be removed from the search index.

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 overview screen of the customer 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 keep-alive connection header for SOAP responses.

en	Enables customers to create their own accounts.

en	Enables fetch S/MIME from CustomerUser backend support.

en	Enables ticket bulk action feature for the agent frontend to work on more than one ticket at a time.

en	Enables ticket bulk action feature only for the listed groups.

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

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	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	Filter for debugging Transitions. Note: More filters can be added in the format <OTRS_TICKET_Attribute> e.g. <OTRS_TICKET_Priority>.

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	Frontend module registration (disable ticket processes screen if no process available) for Customer.

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	German stop words for fulltext index. These words will be removed from the search index.

en	Global Search Module.

en	Good PGP signature.
pt-br	Adicionar Assinatura

en	Graph: Stacked Area Chart

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 skin for visually impaired users.

en	If "HTTPBasicAuth" was selected for Customer::AuthModule, you can specify (by using a RegExp) to strip parts of REMOTE_USER (e. g. for to remove trailing domains). RegExp-Note, $1 will be the new Login.

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 "LDAP" was selected, you can add a filter to each LDAP query, e.g. (mail=*), (objectclass=user) or (!objectclass=computer).

en	If "SysLog" was selected for LogModule, a special log facility can be specified.

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

en	If enabled debugging information for transitions is logged.

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

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

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

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 regex matches, no message will be send by the autoresponder.

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	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	Inline

en	It is possible to configure different skins, for example to distinguish between diferent agents, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex.

en	It is possible to configure different skins, for example to distinguish between diferent customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex.

en	It is possible to configure different themes, for example to distinguish between agents and customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid theme on your system. Please see the example entries for the proper form of the regex.

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	JavaScript function for the search frontend.

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

en	List of JS files to always be loaded for the customer 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	Makes the application block external content loading.

en	Makes the session management use html cookies. If html cookies are disabled or if the client browser disabled html cookies, then the system will work as usual and append the session id to the links.

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

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

en	Maximum number of tickets to be displayed in the result of a search in the customer interface.

en	Minute

en	Module for To-selection in new ticket screen in the customer interface.

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

en	Module to filter and manipulate incoming messages. Get a 4 digit number to ticket free text, use regex in Match e. g. From => '(.+?)@.+?', and use () as [***] in Set =>.

en	Module to generate html OpenSearch profile for short ticket search in the agent interface.

en	Module to generate html OpenSearch profile for short ticket search in the customer interface.

en	No public key found.
pt-br	Nenhum dado de chamado encontrado.

en	No valid OpenPGP data found.
pt-br	Nenhum dado de chamado encontrado.

en	Number of tickets to be displayed in each page of a search result in the customer interface.

en	OTRS can use one or more readonly mirror databases for expensive operations like fulltext search or statistics generation. Here you can specify the DSN for the first mirror database.

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

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 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	Picture-Upload

en	Process Ticket.

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

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	Removes old generic interface debug log entries created before the specified amount of days.

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

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

en	Required permissions to use the ticket merge screen of a zoomed ticket in the agent interface.

en	Required permissions to use the ticket owner screen of a zoomed ticket in the agent interface.

en	Required permissions to use the ticket pending screen of a zoomed ticket in the agent interface.

en	Required permissions to use the ticket priority screen of a zoomed ticket in the agent interface.

en	Romanian

en	Search backend default router.

en	Search backend router.

en	Sent auto follow-up to "%s".

en	Sent auto reject to "%s".

en	Sent auto reply to "%s".

en	Set the default height (in pixels) of inline HTML articles in AgentTicketZoom.

en	Set the maximum height (in pixels) of inline HTML articles in AgentTicketZoom.

en	Sets the default body text for notes added in the ticket owner screen of a zoomed ticket in the agent interface.

en	Sets the default body text for notes added in the ticket pending screen of a zoomed ticket in the agent interface.

en	Sets the default body text for notes added in the ticket priority screen of a zoomed ticket in the agent interface.

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 subject for notes added in the ticket owner screen of a zoomed ticket in the agent interface.

en	Sets the default subject for notes added in the ticket pending screen of a zoomed ticket in the agent interface.

en	Sets the default subject for notes added in the ticket priority screen of a zoomed ticket in the agent interface.

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

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

en	Sets the prefix to the scripts folder on the server, as configured on the web server. This setting is used as a variable, OTRS_CONFIG_ScriptAlias which is found in all forms of messaging used by the application, to build links to the tickets within the system.

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

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

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

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

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

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

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

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

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

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

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

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 state of a ticket in the ticket bulk 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 owner in the ticket bulk screen of the agent interface.

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

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

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

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

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	Show the current owner in the customer interface.

en	Show the current queue in the customer interface.

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 to see a zoomed email ticket in plain text.

en	Shows a list of all the involved agents on this ticket, in the ticket pending screen of a zoomed ticket in the agent interface.

en	Shows a list of all the involved agents on this ticket, in the ticket priority screen of a zoomed ticket in the agent interface.

en	Shows a list of all the possible agents (all agents with note permissions on the queue/ticket) to determine who should be informed about this note, in the ticket owner screen of a zoomed ticket in the agent interface.

en	Shows a list of all the possible agents (all agents with note permissions on the queue/ticket) to determine who should be informed about this note, in the ticket pending screen of a zoomed ticket in the agent interface.

en	Shows a list of all the possible agents (all agents with note permissions on the queue/ticket) to determine who should be informed about this note, in the ticket priority screen of a zoomed ticket in the agent interface.

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 customer zoom view.

en	Shows either the last customer article's subject or the ticket title in the small format overview.

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 ticket priority options in the ticket bulk screen of the agent interface.

en	Shows the ticket priority options in the ticket owner screen of a zoomed ticket in the agent interface.

en	Shows the ticket priority options in the ticket pending screen of a zoomed ticket in the agent interface.

en	Shows the ticket priority options in the ticket priority screen of a zoomed ticket in 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	Signature data.
pt-br	Assinatura atualizada!

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

en	Specifies the group where the user needs rw permissions so that he can access the "SwitchToCustomer" feature.

en	The PGP signature is expired.
pt-br	A assinatura para respostas por e-mail.

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 customer skin's InternalName which should be used in the customer interface. Please check the available skins in Frontend::Customer::Skins.

en	The daemon registration for the system configuration deployment sync manager.

en	The headline shown in the customer interface.

en	The logo shown in the header of the agent interface for the skin "ivory". See "AgentLogo" for further description.

en	The logo shown in the header of the agent interface for the skin "ivory-slim". See "AgentLogo" for further description.

en	The logo shown in the header of the customer 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 value of the From field

en	This is the default orange - black skin for the customer interface.

en	This is the default orange - black skin.

en	This key is not certified with a trusted signature!
pt-br	Há outra campo com o mesmo nome.

en	This module and its PreRun() function will be executed, if defined, for every request. This module is useful to check some user options or to display news about new applications.