diff options
Diffstat (limited to 'rt/etc/RT_Config.pm.in')
| -rw-r--r-- | rt/etc/RT_Config.pm.in | 1106 |
1 files changed, 689 insertions, 417 deletions
diff --git a/rt/etc/RT_Config.pm.in b/rt/etc/RT_Config.pm.in index 498e53c71..fd976de1f 100644 --- a/rt/etc/RT_Config.pm.in +++ b/rt/etc/RT_Config.pm.in @@ -115,19 +115,40 @@ Set($Timezone, "US/Eastern"); =item C<@Plugins> -Set C<@Plugins> to a list of external RT plugins that should be -enabled (those plugins have to be previously downloaded and -installed). +Once a plugin has been downloaded and installed, use C<Plugin()> to add +to the enabled C<@Plugins> list: -Example: + Plugin( "RT::Extension::SLA" ); + Plugin( "RT::Authen::ExternalAuth" ); -C<Set(@Plugins, (qw(RT::Extension::SLA RT::Authen::ExternalAuth)));> +RT will also accept the distribution name (i.e. C<RT-Extension-SLA>) +instead of the package name (C<RT::Extension::SLA>). =cut Set(@Plugins, (qw(RTx::Calendar RT::Extension::MobileUI))); #RTx::Checklist )); +=item C<@StaticRoots> + +Set C<@StaticRoots> to serve extra paths with a static handler. The +contents of each hashref should be the the same arguments as +L<Plack::Middleware::Static> takes. These paths will be checked before +any plugin or core static paths. + +Example: + + Set( @StaticRoots, + { + path => qr{^/static/}, + root => '/local/path/to/static/parent', + }, + ); + +=cut + +Set( @StaticRoots, () ); + =back @@ -140,7 +161,7 @@ Set(@Plugins, (qw(RTx::Calendar =item C<$DatabaseType> Database driver being used; case matters. Valid types are "mysql", -"Oracle" and "Pg". +"Oracle", and "Pg". "SQLite" is also available for non-production use. =cut @@ -194,15 +215,39 @@ SID and database objects are created in C<$DatabaseUser>'s schema. Set($DatabaseName, q{@DB_DATABASE@}); -=item C<$DatabaseRequireSSL> +=item C<%DatabaseExtraDSN> + +Allows additional properties to be passed to the database connection +step. Possible properties are specific to the database-type; see +https://metacpan.org/pod/DBI#connect + +For PostgreSQL, for instance, the following enables SSL (but does no +certificate checking, providing data hiding but no MITM protection): + + # See https://metacpan.org/pod/DBD::Pg#connect + # and http://www.postgresql.org/docs/8.4/static/libpq-ssl.html + Set( %DatabaseExtraDSN, sslmode => 'require' ); + +For MySQL, the following acts similarly if the server has enabled SSL. +Otherwise, it provides no protection; MySQL provides no way to I<force> +SSL connections: + + # See https://metacpan.org/pod/DBD::mysql#connect + # and http://dev.mysql.com/doc/refman/5.1/en/ssl-options.html + Set( %DatabaseExtraDSN, mysql_ssl => 1 ); + +=cut + +Set(%DatabaseExtraDSN, ()); + +=item C<$DatabaseAdmin> -If you're using PostgreSQL and have compiled in SSL support, set -C<$DatabaseRequireSSL> to 1 to turn on SSL communication with the -database. +The name of the database administrator to connect to the database as +during upgrades. =cut -Set($DatabaseRequireSSL, undef); +Set($DatabaseAdmin, "@DB_DBA@"); =back @@ -222,7 +267,7 @@ message. =over 4 -=item C<$LogToSyslog>, C<$LogToScreen> +=item C<$LogToSyslog>, C<$LogToSTDERR> The minimum level error that will be logged to the specific device. From lowest to highest priority, the levels are: @@ -240,7 +285,7 @@ in your web server's error logs). =cut Set($LogToSyslog, "info"); -Set($LogToScreen, "info"); +Set($LogToSTDERR, "info"); =item C<$LogToFile>, C<$LogDir>, C<$LogToFileNamed> @@ -275,11 +320,9 @@ Set($LogStackTraces, ""); =item C<@LogToSyslogConf> -On Solaris or UnixWare, set to ( socket => 'inet' ). Options here -override any other options RT passes to L<Log::Dispatch::Syslog>. -Other interesting flags include facility and logopt. (See the -L<Log::Dispatch::Syslog> documentation for more information.) (Maybe -ident too, if you have multiple RT installations.) +Additional options to pass to L<Log::Dispatch::Syslog>; the most +interesting flags include C<facility>, C<logopt>, and possibly C<ident>. +See the L<Log::Dispatch::Syslog> documentation for more information. =cut @@ -301,14 +344,7 @@ queue-specific subject tags, you'll likely never have to change this configuration. Be B<very careful> with it. Note that it overrides C<$rtname> for -subject token matching and that you should use only "non-capturing" -parenthesis grouping. For example: - -C<Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/i );> - -and NOT - -C<Set($EmailSubjectTagRegex, qr/(example.com|example.org)/i );> +subject token matching. The setting below would make RT behave exactly as it does without the setting enabled. @@ -320,8 +356,10 @@ setting enabled. =item C<$OwnerEmail> C<$OwnerEmail> is the address of a human who manages RT. RT will send -errors generated by the mail gateway to this address. This address -should I<not> be an address that's managed by your RT instance. +errors generated by the mail gateway to this address; it will also be +displayed as the contact person on the RT's login page. Because RT +sends errors to this address, it should I<not> be an address that's +managed by your RT instance, to avoid mail loops. =cut @@ -350,11 +388,14 @@ Set($StoreLoops, undef); C<$MaxAttachmentSize> sets the maximum size (in bytes) of attachments stored in the database. This setting is irrelevant unless one of -$TruncateLongAttachments or $DropLongAttachments (below) are set. +$TruncateLongAttachments or $DropLongAttachments (below) are set, B<OR> +the database is stored in Oracle. On Oracle, attachments larger than +this can be fully stored, but will be truncated to this length when +read. =cut -Set($MaxAttachmentSize, 10_000_000); +Set($MaxAttachmentSize, 10_000_000); # 10M =item C<$TruncateLongAttachments> @@ -412,38 +453,31 @@ Set($IgnoreCcRegexp, undef); =item C<$CanonicalizeEmailAddressMatch>, C<$CanonicalizeEmailAddressReplace> RT provides functionality which allows the system to rewrite incoming -email addresses. In its simplest form, you can substitute the value -in C<CanonicalizeEmailAddressReplace> for the value in -C<CanonicalizeEmailAddressMatch> (These values are passed to the -C<CanonicalizeEmailAddress> subroutine in F<RT/User.pm>) - -By default, that routine performs a C<s/$Match/$Replace/gi> on any -address passed to it. +email addresses, using L<RT::User/CanonicalizeEmailAddress>. The +default implementation replaces all occurrences of the regular +expression in C<CanonicalizeEmailAddressMatch> with +C<CanonicalizeEmailAddressReplace>, via C<s/$Match/$Replace/gi>. The +most common use of this is to replace C<@something.example.com> with +C<@example.com>. If more complex noramlization is required, +L<RT::User/CanonicalizeEmailAddress> can be overridden to provide it. =cut # Set($CanonicalizeEmailAddressMatch, '@subdomain\.example\.com$'); # Set($CanonicalizeEmailAddressReplace, '@example.com'); -=item C<$CanonicalizeOnCreate> - -Set this to 1 and the create new user page will use the values that -you enter in the form but use the function CanonicalizeUserInfo in -F<RT/User_Local.pm> - -=cut - -Set($CanonicalizeOnCreate, 0); - =item C<$ValidateUserEmailAddresses> -If C<$ValidateUserEmailAddresses> is 1, RT will refuse to create +By default C<$ValidateUserEmailAddresses> is 1, and RT will refuse to create users with an invalid email address (as specified in RFC 2822) or with an email address made of multiple email addresses. +Set this to 0 to skip any email address validation. Doing so may open up +vulnerabilities. + =cut -Set($ValidateUserEmailAddresses, undef); +Set($ValidateUserEmailAddresses, 1); =item C<$NonCustomerEmailRegexp> @@ -515,25 +549,15 @@ Set( $CheckMoreMSMailHeaders, 0); C<$MailCommand> defines which method RT will use to try to send mail. We know that 'sendmailpipe' works fairly well. If 'sendmailpipe' -doesn't work well for you, try 'sendmail'. Other options are 'smtp' -or 'qmail'. - -Note that you should remove the '-t' from C<$SendmailArguments> if you -use 'sendmail' rather than 'sendmailpipe' +doesn't work well for you, try 'sendmail'. 'qmail' is also a supported +value. For testing purposes, or to simply disable sending mail out into the -world, you can set C<$MailCommand> to 'testfile' which writes all mail -to a temporary file. RT will log the location of the temporary file -so you can extract mail from it afterward. - -On shutdown, RT will clean up the temporary file created when using -the 'testfile' option. If testing while the RT server is still running, -you can find the files in the location noted in the log file. If you run -a tool like C<rt-crontool> however, or if you look after stopping the server, -the files will have been deleted when the process completed. If you need to -keep the files for development or debugging, you can manually set -C<< UNLINK => 0 >> where the testfile config is processed in -F<lib/RT/Interface/Email.pm>. +world, you can set C<$MailCommand> to 'mbox' which logs all mail, in +mbox format, to files in F</opt/rt4/var/> based in the process start +time. The 'testfile' option is similar, but the files that it creates +(under /tmp) are temporary, and removed upon process completion; the +format is also not mbox-compatable. =cut @@ -567,7 +591,7 @@ address of the queue as it is handed to sendmail -f. This helps force the From_ header away from www-data or other email addresses that show up in the "Sent by" line in Outlook. -The option is a hash reference of queue name to email address. If +The option is a hash reference of queue id/name to email address. If there is no ticket involved, then the value of the C<Default> key will be used. @@ -715,6 +739,29 @@ will use the address of the current user and remove RT's subject tag. Set($ForwardFromUser, 0); +=item C<$HTMLFormatter> + +RT's default pure-perl formatter may fail to successfully convert even +on some relatively simple HTML; this will result in blank C<text/plain> +parts, which is particuarly unfortunate if HTML templates are not in +use. + +If the optional dependency L<HTML::FormatExternal> is installed, RT will +use external programs to render HTML to plain text. The default is to +try, in order, C<w3m>, C<elinks>, C<html2text>, C<links>, C<lynx>, and +then fall back to the C<core> pure-perl formatter if none are installed. + +Set C<$HTMLFormatter> to one of the above programs (or the full path to +such) to use a different program than the above would choose by default. +Setting this requires that L<HTML::FormatExternal> be installed. + +If the chosen formatter is not in the webserver's $PATH, you may set +this option the full path to one of the aforementioned executables. + +=cut + +Set($HTMLFormatter, undef); + =back =head2 Email dashboards @@ -762,16 +809,13 @@ These options only take effect if C<$MailCommand> is 'sendmail' or =item C<$SendmailArguments> C<$SendmailArguments> defines what flags to pass to C<$SendmailPath> -If you picked 'sendmailpipe', you MUST add a -t flag to -C<$SendmailArguments> These options are good for most sendmail -wrappers and work-a-likes. +These options are good for most sendmail wrappers and work-a-likes. These arguments are good for sendmail brand sendmail 8 and newer: -C<Set($SendmailArguments,"-oi -t -ODeliveryMode=b -OErrorMode=m");> +C<Set($SendmailArguments,"-oi -ODeliveryMode=b -OErrorMode=m");> =cut -#Set($SendmailArguments, "-oi -t"); Set($SendmailArguments, "-oi"); @@ -796,39 +840,6 @@ Set($SendmailPath, "/usr/sbin/sendmail"); =back -=head2 SMTP configuration - -These options only take effect if C<$MailCommand> is 'smtp' - -=over 4 - -=item C<$SMTPServer> - -C<$SMTPServer> should be set to the hostname of the SMTP server to use - -=cut - -Set($SMTPServer, undef); - -=item C<$SMTPFrom> - -C<$SMTPFrom> should be set to the 'From' address to use, if not the -email's 'From' - -=cut - -Set($SMTPFrom, undef); - -=item C<$SMTPDebug> - -C<$SMTPDebug> should be set to 1 to debug SMTP mail sending - -=cut - -Set($SMTPDebug, 0); - -=back - =head2 Other mailers =over 4 @@ -836,7 +847,7 @@ Set($SMTPDebug, 0); =item C<@MailParams> C<@MailParams> defines a list of options passed to $MailCommand if it -is not 'sendmailpipe', 'sendmail', or 'smtp' +is not 'sendmailpipe' or 'sendmail'; =cut @@ -854,15 +865,16 @@ Set(@MailParams, ()); This determines the default stylesheet the RT web interface will use. RT ships with several themes by default: - web2 The default layout for RT 3.8 + rudder The default theme for RT 4.2 aileron The default layout for RT 4.0 + web2 The default layout for RT 3.8 ballard Theme which doesn't rely on JavaScript for menuing This bundled distibution of RT also includes: - freeside3 Integration with Freeside (enabled by default) - freeside2.1 Previous Freeside theme + freeside4 Integration with Freeside (enabled by default) + freeside3 Previous Freeside theme -This value actually specifies a directory in F<share/html/NoAuth/css/> +This value actually specifies a directory in F<share/static/css/> from which RT will try to load the file main.css (which should @import any other files the stylesheet needs). This allows you to easily and cleanly create your own stylesheets to apply to RT. This option can @@ -870,7 +882,7 @@ be overridden by users in their preferences. =cut -Set($WebDefaultStylesheet, "freeside3"); +Set($WebDefaultStylesheet, "freeside4"); =item C<$DefaultQueue> @@ -909,6 +921,48 @@ custom field values from external sources at runtime. Set(@CustomFieldValuesSources, ('RT::CustomFieldValues::Queues')); +=item C<%CustomFieldGroupings> + +This option affects the display of ticket and user custom fields in the +web interface. It does not address the sorting of custom fields within +the groupings; which is controlled by the Ticket Custom Fields tab in +Queue Configuration in the Admin UI. + +A nested datastructure defines how to group together custom fields +under a mix of built-in and arbitrary headings ("groupings"). + +Set C<%CustomFieldGroupings> to a nested structure similar to the following: + + Set(%CustomFieldGroupings, + 'RT::Ticket' => [ + 'Grouping Name' => ['CF Name', 'Another CF'], + 'Another Grouping' => ['Some CF'], + 'Dates' => ['Shipped date'], + ], + 'RT::User' => [ + 'Phones' => ['Fax number'], + ], + ); + +The first level keys are record types for which CFs may be used, and the +values are either hashrefs or arrayrefs -- if arrayrefs, then the +ordering is preserved during display, otherwise groupings are displayed +alphabetically. The second level keys are the grouping names and the +values are array refs containing a list of CF names. + +There are several special built-in groupings which RT displays in +specific places (usually the collapsible box of the same title). The +ordering of these standard groupings cannot be modified. You may also +only append Custom Fields to the list in these boxes, not reorder or +remove core fields. + +For C<RT::Ticket>, these groupings are: C<Basics>, C<Dates>, C<Links>, C<People> + +For C<RT::User>: C<Identity>, C<Access control>, C<Location>, C<Phones> + +Extensions may also add their own built-in groupings, refer to the individual +extension documentation for those. + =item C<$CanonicalizeRedirectURLs> Set C<$CanonicalizeRedirectURLs> to 1 to use C<$WebURL> when @@ -925,32 +979,25 @@ enable this option. Set($CanonicalizeRedirectURLs, 0); -=item C<@JSFiles> +=item C<$CanonicalizeURLsInFeeds> + +Set C<$CanonicalizeURLsInFeeds> to 1 to use C<$WebURL> in feeds +rather than the one we get from request. + +If you use RT behind a reverse proxy, you almost certainly want to +enable this option. -A list of JavaScript files to be included in head. Removing any of -the default entries is not suggested. +=cut + +Set($CanonicalizeURLsInFeeds, 0); -If you're a plugin author, refer to RT->AddJavaScript. +=item C<@JSFiles> + +A list of additional JavaScript files to be included in head. =cut -Set(@JSFiles, qw/ - jquery-1.4.2.min.js - jquery_noconflict.js - jquery-ui-1.8.4.custom.min.js - jquery-ui-timepicker-addon.js - jquery-ui-patch-datepicker.js - jquery.cookie.js - titlebox-state.js - util.js - userautocomplete.js - jquery.event.hover-1.0.js - superfish.js - supersubs.js - jquery.supposition.js - history-folding.js - late.js -/); +Set(@JSFiles, qw//); =item C<$JSMinPath> @@ -977,14 +1024,75 @@ Set(@CSSFiles, qw//); =item C<$UsernameFormat> -This determines how user info is displayed. 'concise' will show one of -either NickName, RealName, Name or EmailAddress, depending on what -exists and whether the user is privileged or not. 'verbose' will show -RealName and EmailAddress. +This determines how user info is displayed. 'concise' will show the +first of RealName, Name or EmailAddress that has a value. 'verbose' will +show EmailAddress, and the first of RealName or Name which is defined. +The default, 'role', uses 'verbose' for unprivileged users, and the Name +followed by the RealName for privileged users. =cut -Set($UsernameFormat, "verbose"); +Set($UsernameFormat, "concise"); + +=item C<$UserSearchResultFormat> + +This controls the display of lists of users returned from the User +Summary Search. The display of users in the Admin interface is +controlled by C<%AdminSearchResultFormat>. + +=cut + +Set($UserSearchResultFormat, + q{ '<a href="__WebPath__/User/Summary.html?id=__id__">__id__</a>/TITLE:#'} + .q{,'<a href="__WebPath__/User/Summary.html?id=__id__">__Name__</a>/TITLE:Name'} + .q{,__RealName__, __EmailAddress__} +); + +=item C<@UserSummaryPortlets> + +A list of portlets to be displayed on the User Summary page. +By default, we show all of the available portlets. +Extensions may provide their own portlets for this page. + +=cut + +Set(@UserSummaryPortlets, (qw/ExtraInfo CreateTicket ActiveTickets InactiveTickets/)); + +=item C<$UserSummaryExtraInfo> + +This controls what information is displayed on the User Summary +portal. By default the user's Real Name, Email Address and Username +are displayed. You can remove these or add more as needed. This +expects a Format string of user attributes. Please note that not all +the attributes are supported in this display because we're not +building a table. + +=cut + +Set($UserSummaryExtraInfo, "RealName, EmailAddress, Name"); + +=item C<$UserSummaryTicketListFormat> + +Control the appearance of the Active and Inactive ticket lists in the +User Summary. + +=cut + +Set($UserSummaryTicketListFormat, q{ + '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__id__</a></B>/TITLE:#', + '<B><A HREF="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject', + Status, + QueueName, + Owner, + Priority, + '__NEWLINE__', + '', + '<small>__Requestors__</small>', + '<small>__CreatedRelative__</small>', + '<small>__ToldRelative__</small>', + '<small>__LastUpdatedRelative__</small>', + '<small>__TimeLeft__</small>' +}); =item C<$WebBaseURL>, C<$WebURL> @@ -1018,7 +1126,7 @@ Define the directory name to be used for images in RT web documents. =cut -Set($WebImagesURL, RT->Config->Get('WebPath') . "/NoAuth/images/"); +Set($WebImagesURL, RT->Config->Get('WebPath') . "/static/images/"); =item C<$LogoURL> @@ -1046,24 +1154,6 @@ will be passed through C<loc> for localization. Set($LogoAltText, "Best Practical Solutions, LLC corporate logo"); -=item C<$LogoImageHeight> - -C<$LogoImageHeight> is the value of the C<height> attribute of the logo -C<img> tag. - -=cut - -Set($LogoImageHeight, 38); - -=item C<$LogoImageWidth> - -C<$LogoImageWidth> is the value of the C<width> attribute of the logo -C<img> tag. - -=cut - -Set($LogoImageWidth, 181); - =item C<$WebNoAuthRegex> What portion of RT's URL space should not require authentication. The @@ -1112,10 +1202,10 @@ RT comes with two TrueType fonts covering most available languages. Set( %ChartFont, - 'zh-cn' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf", - 'zh-tw' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf", - 'ja' => "$RT::BasePath/share/fonts/DroidSansFallback.ttf", - 'others' => "$RT::BasePath/share/fonts/DroidSans.ttf", + 'zh-cn' => "$RT::FontPath/DroidSansFallback.ttf", + 'zh-tw' => "$RT::FontPath/DroidSansFallback.ttf", + 'ja' => "$RT::FontPath/DroidSansFallback.ttf", + 'others' => "$RT::FontPath/DroidSans.ttf", ); =item C<$ChartsTimezonesInDB> @@ -1132,6 +1222,19 @@ At this time, this feature only applies to MySQL and PostgreSQL. Set($ChartsTimezonesInDB, 0); +=item C<@ChartColors> + +An array of 6-digit hexadecimal RGB color values used for chart series. By +default there are 12 distinct colors. + +=cut + +Set(@ChartColors, qw( + 66cc66 ff6666 ffcc66 663399 + 3333cc 339933 993333 996633 + 33cc33 cc3333 cc9933 6633cc +)); + =back @@ -1168,7 +1271,7 @@ user's customized homepage ("RT at a glance"). Set( $HomepageComponents, [ - qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards SavedSearches ) # loc_qw + qw(QuickCreate Quicksearch MyCalendar MyAdminQueues MySupportQueues MyReminders RefreshHomepage Dashboards SavedSearches FindUser ) # loc_qw ] ); @@ -1184,16 +1287,13 @@ Set( =item C<$UseSQLForACLChecks> Historically, ACLs were checked on display, which could lead to empty -search pages and wrong ticket counts. Set C<$UseSQLForACLChecks> to 1 -to limit search results in SQL instead, which eliminates these -problems. - -This option is still relatively new; it may result in performance -problems in some cases, or significant speedups in others. +search pages and wrong ticket counts. Set C<$UseSQLForACLChecks> to 0 +to go back to this method; this will reduce the complexity of the +generated SQL statements, at the cost of the aforementioned bugs. =cut -Set($UseSQLForACLChecks, undef); +Set($UseSQLForACLChecks, 1); =item C<$TicketsItemMapSize> @@ -1234,7 +1334,7 @@ Set ($DefaultSearchResultFormat, qq{ Customer, Status, QueueName, - OwnerName, + Owner, Priority, '__NEWLINE__', '__NBSP__', @@ -1245,6 +1345,23 @@ Set ($DefaultSearchResultFormat, qq{ '<small>__LastUpdatedRelative__</small>', '<small>__TimeLeft__</small>'}); +=item C<$DefaultSearchResultOrderBy> + +What Tickets column should we order by for RT Ticket search results. + +=cut + +Set($DefaultSearchResultOrderBy, 'id'); + +=item C<$DefaultSearchResultOrder> + +When ordering RT Ticket search results by C<$DefaultSearchResultOrderBy>, +should the sort be ascending (ASC) or descending (DESC). + +=cut + +Set($DefaultSearchResultOrder, 'ASC'); + =item C<$DefaultSelfServiceSearchResultFormat> C<$DefaultSelfServiceSearchResultFormat> is the default format of @@ -1257,7 +1374,7 @@ Set($DefaultSelfServiceSearchResultFormat, qq{ '<B><A HREF="__WebPath__/SelfService/Display.html?id=__id__">__Subject__</a></B>/TITLE:Subject', Status, Requestors, - OwnerName}); + Owner}); =item C<%FullTextSearch> @@ -1337,6 +1454,20 @@ Ticket/Display.html. This option can be controlled by users also. Set($MoreAboutRequestorTicketList, "Active"); +=item C<$MoreAboutRequestorTicketListFormat> + +Control the appearance of the ticket lists in the 'More About Requestors' box. + +=cut + +Set($MoreAboutRequestorTicketListFormat, q{ + '<a href="__WebPath__/Ticket/Display.html?id=__id__">__id__</a>', + '__Owner__', + '<a href="__WebPath__/Ticket/Display.html?id=__id__">__Subject__</a>', + '__Status__', +}); + + =item C<$MoreAboutRequestorExtraInfo> By default, the 'More about requestor' box on Ticket/Display.html @@ -1398,6 +1529,12 @@ builder are replaced by text fields that autocomplete. This can alleviate the sometimes huge owner list for installations where many users have the OwnTicket right. +Autocompleter is automatically turned on if list contains more than +50 users, but penalty of executing potentially slow query is still paid. + +Drop down doesn't show unprivileged users. If your setup allows unprivileged +to own ticket then you have to enable autocompleting. + =cut Set($AutocompleteOwners, 0); @@ -1412,15 +1549,19 @@ is ignored. Helpful when owners list is huge in the query builder. Set($AutocompleteOwnersForSearch, 0); -=item C<$UserAutocompleteFields> +=item C<$UserSearchFields> + +Used by the User Autocompleter as well as the User Search. -Specifies which fields of L<RT::User> to match against and how to -match each field when autocompleting users. Valid match methods are -LIKE, STARTSWITH, ENDSWITH, =, and !=. +Specifies which fields of L<RT::User> to match against and how to match +each field when autocompleting users. Valid match methods are LIKE, +STARTSWITH, ENDSWITH, =, and !=. Valid search fields are the core User +fields, as well as custom fields, which are specified as "CF.1234" or +"CF.Name" =cut -Set($UserAutocompleteFields, { +Set($UserSearchFields, { EmailAddress => 'STARTSWITH', Name => 'STARTSWITH', RealName => 'LIKE', @@ -1428,14 +1569,31 @@ Set($UserAutocompleteFields, { =item C<$AllowUserAutocompleteForUnprivileged> -Should unprivileged users be allowed to autocomplete users. Setting -this option to 1 means unprivileged users will be able to search all -your users. +Should unprivileged users (users of SelfService) be allowed to +autocomplete users. Setting this option to 1 means unprivileged users +will be able to search all your users. =cut Set($AllowUserAutocompleteForUnprivileged, 0); +=item C<$TicketAutocompleteFields> + +Specifies which fields of L<RT::Ticket> to match against and how to match each +field when autocompleting users. Valid match methods are LIKE, STARTSWITH, +ENDSWITH, C<=>, and C<!=>. + +Not all Ticket fields are publically accessible and hence won't work for +autocomplete unless you override their accessibility using a local overlay or a +plugin. Out of the box the following fields are public: id, Subject. + +=cut + +Set( $TicketAutocompleteFields, { + id => 'STARTSWITH', + Subject => 'LIKE', +}); + =item C<$DisplayTicketAfterQuickCreate> Enable this to redirect to the created ticket display page @@ -1542,15 +1700,6 @@ for Rich Text settings. Set($MessageBoxWidth, undef); Set($MessageBoxHeight, 15); -=item C<$MessageBoxWrap> - -Wrapping is disabled when using MessageBoxRichText because of a bad -interaction between IE and wrapping with the Rich Text Editor. - -=cut - -Set($MessageBoxWrap, "SOFT"); - =item C<$MessageBoxRichText> Should "rich text" editing be enabled? This option lets your users @@ -1580,7 +1729,7 @@ Set($MessageBoxIncludeSignature, 1); =item C<$MessageBoxIncludeSignatureOnComment> Should your users' signatures (from their Preferences page) be -included in Comments. Setting this to false overrides +included in Comments. Setting this to 0 overrides C<$MessageBoxIncludeSignature>. =cut @@ -1604,15 +1753,39 @@ option can be overridden by users in their preferences. Set($OldestTransactionsFirst, 1); -=item C<$DeferTransactionLoading> +=item C<$ShowHistory> + +This option controls how history is shown on the ticket display page. It +accepts one of three possible modes and is overrideable on a per-user +preference level. If you regularly deal with long tickets and don't care much +about the history, you may wish to change this option to C<click>. + +=over + +=item C<delay> (the default) + +When set to C<delay>, history is loaded via javascript after the rest of the +page has been loaded. This speeds up apparent page load times and generally +provides a smoother experience. You may notice slight delays before the ticket +history appears on very long tickets. + +=item C<click> -When set, defers loading ticket history until the user clicks a link. -This should end up serving pages to users quicker, since generating -all the HTML for transaction history can be slow for long tickets. +When set to C<click>, history is loaded on demand when a placeholder link is +clicked. This speeds up ticket display page loads and history is never loaded +if not requested. + +=item C<always> + +When set to C<always>, history is loaded before showing the page. This ensures +history is always available immediately, but at the expense of longer page load +times. This behaviour was the default in RT 4.0. + +=back =cut -# Set($DeferTransactionLoading, 1); +Set($ShowHistory, 'delay'); =item C<$ShowBccHeader> @@ -1642,28 +1815,24 @@ overrides C<TrustHTMLAttachments>. Set($AlwaysDownloadAttachments, undef); -=item C<$AttachmentUnits> - -Controls the units (kilobytes or bytes) that attachment sizes use for -display. The default is to display kilobytes if the attachment is -larger than 1024 bytes, bytes otherwise. If you set -C<$AttachmentUnits> to C<'k'> then attachment sizes will always be -displayed in kilobytes. If set to C<'b'>, then sizes will be bytes. - -=cut +=item C<$PreferRichText> -Set($AttachmentUnits, undef); +By default, RT shows rich text (HTML) messages if possible. If +C<$PreferRichText> is set to 0, RT will show plain text messages in +preference to any rich text alternatives. -=item C<$PreferRichText> +As a security precaution, RT limits the HTML that is displayed to a +known-good subset -- as allowing arbitrary HTML to be displayed exposes +multiple vectors for XSS and phishing attacks. If +L</$TrustHTMLAttachments> is enabled, the original HTML is available for +viewing via the "Download" link. -If C<$PreferRichText> is set to 1, RT will show HTML/Rich text messages -in preference to their plain-text alternatives. RT "scrubs" the HTML to -show only a minimal subset of HTML to avoid possible contamination by -cross-site-scripting attacks. +If the optional L<HTML::Gumbo> dependency is installed, RT will leverage +this to allow a broader set of HTML through, including tables. =cut -Set($PreferRichText, undef); +Set($PreferRichText, 1); =item C<$MaxInlineBody> @@ -1686,23 +1855,25 @@ behavior. Set($ShowTransactionImages, 1); -=item C<$PlainTextPre> +=item C<$ShowRemoteImages> -Normally plaintext attachments are displayed as HTML with line breaks -preserved. This causes space- and tab-based formatting not to be -displayed correctly. By setting $PlainTextPre messages will be -displayed using <pre>. +By default, RT doesn't show remote images attached to incoming (and outgoing) +ticket updates inline. Set this variable to 1 if you'd like to enable remote +image display. Showing remote images may allow spammers and other senders to +track when messages are viewed and see referer information. -=cut +Note that this setting is independent of L</$ShowTransactionImages> above. -Set($PlainTextPre, 0); +=cut +Set($ShowRemoteImages, 0); =item C<$PlainTextMono> -Set C<$PlainTextMono> to 1 to use monospaced font and preserve -formatting; unlike C<$PlainTextPre>, the text will wrap to fit width -of the browser window; this option overrides C<$PlainTextPre>. +Normally plaintext attachments are displayed as HTML with line breaks +preserved. This causes space- and tab-based formatting not to be +displayed correctly. Set C<$PlainTextMono> to 1 to use a monospaced +font and preserve formatting. =cut @@ -1729,17 +1900,35 @@ provides two formats: link after the URL. * 'httpurl_overwrite': also detects URLs as 'httpurl' format, but - replaces the URL with a link. + replaces the URL with a link. Enabled by default. See F<share/html/Elements/MakeClicky> for documentation on how to add your own styles of link detection. =cut -Set(@Active_MakeClicky, qw()); +Set(@Active_MakeClicky, qw(httpurl_overwrite)); -=back +=item C<$QuoteFolding> + +Quote folding is the hiding of old replies in transaction history. +It defaults to on. Set this to 0 to disable it. + +=cut + +Set($QuoteFolding, 1); + +=item C<$AllowLoginPasswordAutoComplete> +Allow browsers to remember the user's password on login (in case the +browser can do so, and has the appropriate setting enabled). Default +is 0. + +=cut + +Set($AllowLoginPasswordAutoComplete, 0); + +=back =head1 Application logic @@ -1805,8 +1994,9 @@ Set($ApprovalRejectionNotes, 1); =item C<$ForceApprovalsView> Should approval tickets only be viewed and modified through the standard -approval interface? Changing this setting to 1 will redirect any attempt to -use the normal ticket display and modify page for approval tickets. +approval interface? With this setting enabled (by default), any attempt to use +the normal ticket display and modify page for approval tickets will be +redirected. For example, with this option set to 1 and an approval ticket #123: @@ -1816,11 +2006,13 @@ is redirected to /Approval/Display.html?id=123 +With this option set to 0, the redirect won't happen. + =back =cut -Set($ForceApprovalsView, 0); +Set($ForceApprovalsView, 1); =head1 Extra security @@ -1832,7 +2024,7 @@ defaults alone. =item C<$DisallowExecuteCode> -If set to a true value, the C<ExecuteCode> right will be removed from +If set to 1, the C<ExecuteCode> right will be removed from all users, B<including> the superuser. This is intended for when RT is installed into a shared environment where even the superuser should not be allowed to run arbitrary Perl code on the server via scrips. @@ -1843,7 +2035,7 @@ Set($DisallowExecuteCode, 0); =item C<$Framebusting> -If set to a false value, framekiller javascript will be disabled and the +If set to 0, framekiller javascript will be disabled and the X-Frame-Options: DENY header will be suppressed from all responses. This disables RT's clickjacking protection. @@ -1853,7 +2045,7 @@ Set($Framebusting, 1); =item C<$RestrictReferrer> -If set to a false value, the HTTP C<Referer> (sic) header will not be +If set to 0, the HTTP C<Referer> (sic) header will not be checked to ensure that requests come from RT's own domain. As RT allows for GET requests to alter state, disabling this opens RT up to cross-site request forgery (CSRF) attacks. @@ -1864,9 +2056,9 @@ Set($RestrictReferrer, 1); =item C<$RestrictLoginReferrer> -If set to a false value, RT will allow the user to log in from any link +If set to 0, RT will allow the user to log in from any link or request, merely by passing in C<user> and C<pass> parameters; setting -it to a true value forces all logins to come from the login box, so the +it to 1 forces all logins to come from the login box, so the user is aware that they are being logged in. The default is off, for backwards compatability. @@ -1901,6 +2093,17 @@ Simple wildcards, similar to SSL certificates, are allowed. For example: Set(@ReferrerWhitelist, qw()); + +=item C<$BcryptCost> + +This sets the default cost parameter used for the C<bcrypt> key +derivation function. Valid values range from 4 to 31, inclusive, with +higher numbers denoting greater effort. + +=cut + +Set($BcryptCost, 10); + =back @@ -1909,74 +2112,89 @@ Set(@ReferrerWhitelist, qw()); =over 4 -=item C<$WebExternalAuth> +=item C<$WebRemoteUserAuth> -If C<$WebExternalAuth> is defined, RT will defer to the environment's -REMOTE_USER variable. +If C<$WebRemoteUserAuth> is defined, RT will defer to the environment's +REMOTE_USER variable, which should be set by the webserver's +authentication layer. =cut -Set($WebExternalAuth, undef); +Set($WebRemoteUserAuth, undef); -=item C<$WebExternalAuthContinuous> +=item C<$WebRemoteUserContinuous> -If C<$WebExternalAuthContinuous> is defined, RT will check for the +If C<$WebRemoteUserContinuous> is defined, RT will check for the REMOTE_USER on each access. If you would prefer this to only happen -once (at initial login) set this to a false value. The default -setting will help ensure that if your external authentication system +once (at initial login) set this to 0. The default +setting will help ensure that if your webserver's authentication layer deauthenticates a user, RT notices as soon as possible. =cut -Set($WebExternalAuthContinuous, 1); +Set($WebRemoteUserContinuous, 1); -=item C<$WebFallbackToInternalAuth> +=item C<$WebFallbackToRTLogin> -If C<$WebFallbackToInternalAuth> is defined, the user is allowed a +If C<$WebFallbackToRTLogin> is defined, the user is allowed a chance of fallback to the login screen, even if REMOTE_USER failed. =cut -Set($WebFallbackToInternalAuth, undef); +Set($WebFallbackToRTLogin, undef); -=item C<$WebExternalGecos> +=item C<$WebRemoteUserGecos> -C<$WebExternalGecos> means to match 'gecos' field as the user -identity); useful with mod_auth_pwcheck and IIS Integrated Windows -logon. +C<$WebRemoteUserGecos> means to match 'gecos' field as the user +identity; useful with C<mod_auth_external>. =cut -Set($WebExternalGecos, undef); +Set($WebRemoteUserGecos, undef); -=item C<$WebExternalAuto> +=item C<$WebRemoteUserAutocreate> -C<$WebExternalAuto> will create users under the same name as -REMOTE_USER upon login, if it's missing in the Users table. +C<$WebRemoteUserAutocreate> will create users under the same name as +REMOTE_USER upon login, if they are missing from the Users table. =cut -Set($WebExternalAuto, undef); +Set($WebRemoteUserAutocreate, undef); -=item C<$AutoCreate> +=item C<$UserAutocreateDefaultsOnLogin> -If C<$WebExternalAuto> is set to 1, C<$AutoCreate> will be passed to -User's Create method. Use it to set defaults, such as creating -Unprivileged users with C<{ Privileged => 0 }> This must be a hashref. +If C<$WebRemoteUserAutocreate> is set to 1, C<$UserAutocreateDefaultsOnLogin> +will be passed to L<RT::User/Create>. Use it to set defaults, such as +creating unprivileged users with C<<{ Privileged => 0 }>>. This must be +a hashref. =cut -Set($AutoCreate, undef); +Set($UserAutocreateDefaultsOnLogin, undef); =item C<$WebSessionClass> -C<$WebSessionClass> is the class you wish to use for managing sessions. -It defaults to use your SQL database, except on Oracle, where it -defaults to files on disk. +C<$WebSessionClass> is the class you wish to use for storing sessions. On +MySQL, Pg, and Oracle it defaults to using your database, in other cases +sessions are stored in files using L<Apache::Session::File>. Other installed +Apache::Session::* modules can be used to store sessions. + + Set($WebSessionClass, "Apache::Session::File"); =cut -# Set($WebSessionClass, "Apache::Session::File"); +Set($WebSessionClass, undef); + +=item C<%WebSessionProperties> + +C<%WebSessionProperties> is the hash to configure class L</$WebSessionClass> +in case custom class is used. By default it's empty and values are picked +depending on the class. Make sure that it's empty if you're using DB as session +backend. + +=cut + +Set( %WebSessionProperties ); =item C<$AutoLogoff> @@ -2149,12 +2367,139 @@ them. Set($SimpleSearchIncludeResolved, 0); +=item C<$TimeInICal> + +By default, events in the iCal feed on the ticket search page +contain only dates, making them all day calendar events. Set +C<$TimeInICal> if you have start or due dates on tickets that +have significant time values and you want those times to be +included in the events in the iCal feed. + +This option can also be set as an individual user preference. + +=cut + +Set($TimeInICal, 0); + =back +=head1 Cryptography + +A complete description of RT's cryptography capabilities can be found in +L<RT::Crypt>. At this moment, GnuPG (PGP) and SMIME security protocols are +supported. + +=over 4 + +=item C<%Crypt> + +The following options apply to all cryptography protocols. + +By default, all enabled security protocols will analyze each incoming +email. You may set C<Incoming> to a subset of this list, if some enabled +protocols do not apply to incoming mail; however, this is usually +unnecessary. Note that for any verification or decryption to occur for +incoming mail, the C<Auth::Crypt> mail plugin must be added to +L</@MailPlugins> as specified in L<RT::Crypt/Handling incoming messages>. + +For outgoing emails, the first security protocol from the above list is +used. Use the C<Outgoing> option to set a security protocol that should +be used in outgoing emails. At this moment, only one protocol can be +used to protect outgoing emails. + +Set C<RejectOnUnencrypted> to 1 if all incoming email must be +properly encrypted. All unencrypted emails will be rejected by RT. + +Set C<RejectOnMissingPrivateKey> to 0 if you don't want to reject +emails encrypted for key RT doesn't have and can not decrypt. + +Set C<RejectOnBadData> to 0 if you don't want to reject letters +with incorrect data. + +If you want to allow people to encrypt attachments inside the DB then +set C<AllowEncryptDataInDB> to 1. + +Set C<Dashboards> to a hash with Encrypt and Sign keys to control +whether dashboards should be encrypted and/or signed correspondingly. +By default they are not encrypted or signed. + +=back + +=cut -=head1 GnuPG integration +Set( %Crypt, + Incoming => undef, # ['GnuPG', 'SMIME'] + Outgoing => undef, # 'SMIME' + + RejectOnUnencrypted => 0, + RejectOnMissingPrivateKey => 1, + RejectOnBadData => 1, + + AllowEncryptDataInDB => 0, + + Dashboards => { + Encrypt => 0, + Sign => 0, + }, +); + +=head2 SMIME configuration + +A full description of the SMIME integration can be found in +L<RT::Crypt::SMIME>. + +=over 4 + +=item C<%SMIME> + +Set C<Enable> to 0 or 1 to disable or enable SMIME for +encrypting and signing messages. + +Set C<OpenSSL> to path to F<openssl> executable. + +Set C<Keyring> to directory with key files. Key and certificates should +be stored in a PEM file in this directory named named, e.g., +F<email.address@example.com.pem>. + +Set C<CAPath> to either a PEM-formatted certificate of a single signing +certificate authority, or a directory of such (including hash symlinks +as created by the openssl tool C<c_rehash>). Only SMIME certificates +signed by these certificate authorities will be treated as valid +signatures. If left unset (and C<AcceptUntrustedCAs> is unset, as it is +by default), no signatures will be marked as valid! + +Set C<AcceptUntrustedCAs> to allow arbitrary SMIME certificates, no +matter their signing entities. Such mails will be marked as untrusted, +but signed; C<CAPath> will be used to mark which mails are signed by +trusted certificate authorities. This configuration is generally +insecure, as it allows the possibility of accepting forged mail signed +by an untrusted certificate authority. + +Setting C<AcceptUntrustedCAs> also allows encryption to users with +certificates created by untrusted CAs. + +Set C<Passphrase> to a scalar (to use for all keys), an anonymous +function, or a hash (to look up by address). If the hash is used, the +'' key is used as a default. + +See L<RT::Crypt::SMIME> for details. + +=back + +=cut + +Set( %SMIME, + Enable => @RT_SMIME@, + OpenSSL => 'openssl', + Keyring => q{@RT_VAR_PATH@/data/smime}, + CAPath => undef, + AcceptUntrustedCAs => undef, + Passphrase => undef, +); + +=head2 GnuPG configuration A full description of the (somewhat extensive) GnuPG integration can be found by running the command `perldoc L<RT::Crypt::GnuPG>` (or @@ -2164,27 +2509,25 @@ be found by running the command `perldoc L<RT::Crypt::GnuPG>` (or =item C<%GnuPG> -Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and -signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format. +Set C<Enable> to 0 or 1 to disable or enable GnuPG interfaces +for encrypting and signing outgoing messages. -If you want to allow people to encrypt attachments inside the DB then -set C<AllowEncryptDataInDB> to 1. +Set C<GnuPG> to the name or path of the gpg binary to use. -Set C<RejectOnMissingPrivateKey> to false if you don't want to reject -emails encrypted for key RT doesn't have and can not decrypt. +Set C<Passphrase> to a scalar (to use for all keys), an anonymous +function, or a hash (to look up by address). If the hash is used, the +'' key is used as a default. -Set C<RejectOnBadData> to false if you don't want to reject letters -with incorrect GnuPG data. +Set C<OutgoingMessagesFormat> to 'inline' to use inline encryption and +signatures instead of 'RFC' (GPG/MIME: RFC3156 and RFC1847) format. =cut Set(%GnuPG, - Enable => @RT_GPG@, + Enable => @RT_GPG@, + GnuPG => 'gpg', + Passphrase => undef, OutgoingMessagesFormat => "RFC", # Inline - AllowEncryptDataInDB => 0, - - RejectOnMissingPrivateKey => 1, - RejectOnBadData => 1, ); =item C<%GnuPGOptions> @@ -2204,9 +2547,6 @@ Set(%GnuPGOptions, # URL of a keyserver # keyserver => 'hkp://subkeys.pgp.net', -# enables the automatic retrieving of keys when encrypting -# 'auto-key-locate' => 'keyserver', - # enables the automatic retrieving of keys when verifying signatures # 'keyserver-options' => 'auto-key-retrieve', ); @@ -2348,6 +2688,14 @@ all possible transitions in each lifecycle using the following format: ... }, +The order of items in the listing for each transition line affects +the order they appear in the drop-down. If you change the config +for 'open' state listing to: + + open => [qw(stalled rejected deleted resolved)], + +then the 'resolved' status will appear as the last item in the drop-down. + =head3 Statuses available during ticket creation By default users can create tickets with a status of new, @@ -2450,8 +2798,8 @@ For example: Unless there is an explicit mapping between statuses in two different lifecycles, you can not move tickets between queues with these -lifecycles. This is true even if the different lifecycles use the exact -same set of statuses. Such a mapping is defined as follows: +lifecycles -- even if both use the exact same set of statuses. +Such a mapping is defined as follows: __maps__ => { 'from lifecycle -> to lifecycle' => { @@ -2465,9 +2813,9 @@ same set of statuses. Such a mapping is defined as follows: Set(%Lifecycles, default => { - initial => [ 'new' ], - active => [ 'open', 'stalled' ], - inactive => [ 'resolved', 'rejected', 'deleted' ], + initial => [qw(new)], # loc_qw + active => [qw(open stalled)], # loc_qw + inactive => [qw(resolved rejected deleted)], # loc_qw defaults => { on_create => 'new', @@ -2479,64 +2827,32 @@ Set(%Lifecycles, }, transitions => { - '' => [qw(new open resolved)], + "" => [qw(new open resolved)], # from => [ to list ], - new => [qw(open stalled resolved rejected deleted)], - open => [qw(new stalled resolved rejected deleted)], - stalled => [qw(new open rejected resolved deleted)], - resolved => [qw(new open stalled rejected deleted)], - rejected => [qw(new open stalled resolved deleted)], - deleted => [qw(new open stalled rejected resolved)], + new => [qw( open stalled resolved rejected deleted)], + open => [qw(new stalled resolved rejected deleted)], + stalled => [qw(new open rejected resolved deleted)], + resolved => [qw(new open stalled rejected deleted)], + rejected => [qw(new open stalled resolved deleted)], + deleted => [qw(new open stalled rejected resolved )], }, rights => { '* -> deleted' => 'DeleteTicket', '* -> *' => 'ModifyTicket', }, actions => [ - 'new -> open' => { - label => 'Open It', # loc - update => 'Respond', - }, - 'new -> resolved' => { - label => 'Resolve', # loc - update => 'Comment', - }, - 'new -> rejected' => { - label => 'Reject', # loc - update => 'Respond', - }, - 'new -> deleted' => { - label => 'Delete', # loc - }, - - 'open -> stalled' => { - label => 'Stall', # loc - update => 'Comment', - }, - 'open -> resolved' => { - label => 'Resolve', # loc - update => 'Comment', - }, - 'open -> rejected' => { - label => 'Reject', # loc - update => 'Respond', - }, - - 'stalled -> open' => { - label => 'Open It', # loc - }, - 'resolved -> open' => { - label => 'Re-open', # loc - update => 'Comment', - }, - 'rejected -> open' => { - label => 'Re-open', # loc - update => 'Comment', - }, - 'deleted -> open' => { - label => 'Undelete', # loc - }, + 'new -> open' => { label => 'Open It', update => 'Respond' }, # loc{label} + 'new -> resolved' => { label => 'Resolve', update => 'Comment' }, # loc{label} + 'new -> rejected' => { label => 'Reject', update => 'Respond' }, # loc{label} + 'new -> deleted' => { label => 'Delete', }, # loc{label} + 'open -> stalled' => { label => 'Stall', update => 'Comment' }, # loc{label} + 'open -> resolved' => { label => 'Resolve', update => 'Comment' }, # loc{label} + 'open -> rejected' => { label => 'Reject', update => 'Respond' }, # loc{label} + 'stalled -> open' => { label => 'Open It', }, # loc{label} + 'resolved -> open' => { label => 'Re-open', update => 'Comment' }, # loc{label} + 'rejected -> open' => { label => 'Re-open', update => 'Comment' }, # loc{label} + 'deleted -> open' => { label => 'Undelete', }, # loc{label} ], }, # don't change lifecyle of the approvals, they are not capable to deal with @@ -2570,49 +2886,17 @@ Set(%Lifecycles, '* -> *' => 'ModifyTicket', }, actions => [ - 'new -> open' => { - label => 'Open It', # loc - update => 'Respond', - }, - 'new -> resolved' => { - label => 'Resolve', # loc - update => 'Comment', - }, - 'new -> rejected' => { - label => 'Reject', # loc - update => 'Respond', - }, - 'new -> deleted' => { - label => 'Delete', # loc - }, - - 'open -> stalled' => { - label => 'Stall', # loc - update => 'Comment', - }, - 'open -> resolved' => { - label => 'Resolve', # loc - update => 'Comment', - }, - 'open -> rejected' => { - label => 'Reject', # loc - update => 'Respond', - }, - - 'stalled -> open' => { - label => 'Open It', # loc - }, - 'resolved -> open' => { - label => 'Re-open', # loc - update => 'Comment', - }, - 'rejected -> open' => { - label => 'Re-open', # loc - update => 'Comment', - }, - 'deleted -> open' => { - label => 'Undelete', # loc - }, + 'new -> open' => { label => 'Open It', update => 'Respond' }, # loc{label} + 'new -> resolved' => { label => 'Resolve', update => 'Comment' }, # loc{label} + 'new -> rejected' => { label => 'Reject', update => 'Respond' }, # loc{label} + 'new -> deleted' => { label => 'Delete', }, # loc{label} + 'open -> stalled' => { label => 'Stall', update => 'Comment' }, # loc{label} + 'open -> resolved' => { label => 'Resolve', update => 'Comment' }, # loc{label} + 'open -> rejected' => { label => 'Reject', update => 'Respond' }, # loc{label} + 'stalled -> open' => { label => 'Open It', }, # loc{label} + 'resolved -> open' => { label => 'Re-open', update => 'Comment' }, # loc{label} + 'rejected -> open' => { label => 'Re-open', update => 'Comment' }, # loc{label} + 'deleted -> open' => { label => 'Undelete', }, # loc{label} ], }, ); @@ -2629,7 +2913,7 @@ Set(%Lifecycles, RT can show administrators a feed of recent RT releases and other related announcements and information from Best Practical on the top -level Configuration page. This feature helps you stay up to date on +level Admin page. This feature helps you stay up to date on RT security announcements and version updates. RT provides this feature using an "iframe" on C</Admin/index.html> @@ -2637,7 +2921,7 @@ which asks the administrator's browser to show an inline page from Best Practical's website. If you'd rather not make this feature available to your -administrators, set C<$ShowRTPortal> to a false value. +administrators, set C<$ShowRTPortal> to 0. =cut @@ -2655,41 +2939,53 @@ Set(%AdminSearchResultFormat, Queues => q{'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__id__</a>/TITLE:#'} .q{,'<a href="__WebPath__/Admin/Queues/Modify.html?id=__id__">__Name__</a>/TITLE:Name'} - .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Disabled__,__Lifecycle__}, + .q{,__Description__,__Address__,__Priority__,__DefaultDueIn__,__Lifecycle__,__SubjectTag__,__Disabled__}, Groups => q{'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__id__</a>/TITLE:#'} .q{,'<a href="__WebPath__/Admin/Groups/Modify.html?id=__id__">__Name__</a>/TITLE:Name'} - .q{,'__Description__'}, + .q{,'__Description__',__Disabled__}, Users => q{'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__id__</a>/TITLE:#'} .q{,'<a href="__WebPath__/Admin/Users/Modify.html?id=__id__">__Name__</a>/TITLE:Name'} - .q{,__RealName__, __EmailAddress__}, + .q{,__RealName__, __EmailAddress__,__Disabled__}, CustomFields => q{'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__id__</a>/TITLE:#'} .q{,'<a href="__WebPath__/Admin/CustomFields/Modify.html?id=__id__">__Name__</a>/TITLE:Name'} - .q{,__AppliedTo__, __FriendlyType__, __FriendlyPattern__}, + .q{,__AddedTo__, __FriendlyType__, __FriendlyPattern__,__Disabled__}, Scrips => - q{'<a href="__WebPath__/Admin/Queues/Scrip.html?id=__id__&Queue=__QueueId__">__id__</a>/TITLE:#'} - .q{,'<a href="__WebPath__/Admin/Queues/Scrip.html?id=__id__&Queue=__QueueId__">__Description__</a>/TITLE:Description'} - .q{,__Stage__, __Condition__, __Action__, __Template__}, - - GlobalScrips => - q{'<a href="__WebPath__/Admin/Global/Scrip.html?id=__id__">__id__</a>/TITLE:#'} - .q{,'<a href="__WebPath__/Admin/Global/Scrip.html?id=__id__">__Description__</a>/TITLE:Description'} - .q{,__Stage__, __Condition__, __Action__, __Template__}, + q{'<a href="__WebPath__/Admin/Scrips/Modify.html?id=__id____From__">__id__</a>/TITLE:#'} + .q{,'<a href="__WebPath__/Admin/Scrips/Modify.html?id=__id____From__">__Description__</a>/TITLE:Description'} + .q{,__Condition__, __Action__, __Template__, __Disabled__}, Templates => q{'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__id__</a>/TITLE:#'} .q{,'<a href="__WebPath__/__WebRequestPathDir__/Template.html?Queue=__QueueId__&Template=__id__">__Name__</a>/TITLE:Name'} - .q{,'__Description__'}, + .q{,'__Description__','__UsedBy__','__IsEmpty__'}, Classes => q{ '<a href="__WebPath__/Admin/Articles/Classes/Modify.html?id=__id__">__id__</a>/TITLE:#'} .q{,'<a href="__WebPath__/Admin/Articles/Classes/Modify.html?id=__id__">__Name__</a>/TITLE:Name'} - .q{,__Description__}, + .q{,__Description__,__Disabled__}, +); + +=item C<%AdminSearchResultRows> + +Use C<%AdminSearchResultRows> to define the search result rows in the admin +interface on a per-RT-class basis. + +=cut + +Set(%AdminSearchResultRows, + Queues => 50, + Groups => 50, + Users => 50, + CustomFields => 50, + Scrips => 50, + Templates => 50, + Classes => 50, ); =back @@ -2741,7 +3037,7 @@ be added while the server is running. =cut -Set($DevelMode, "@RT_DEVEL_MODE@"); +Set($DevelMode, 0); =item C<$RecordBaseClass> @@ -2777,7 +3073,7 @@ C<$StatementLog> to be the level that you wish SQL statements to be logged at. Enabling this option will also expose the SQL Queries page in the -Configuration -> Tools menu for SuperUsers. +Admin -> Tools menu for SuperUsers. =cut @@ -2785,30 +3081,6 @@ Set($StatementLog, undef); =back - - - -=head1 Deprecated options - -=over 4 - -=item C<$LinkTransactionsRun1Scrip> - -RT-3.4 backward compatibility setting. Add/Delete Link used to record -one transaction and run one scrip. Set this value to 1 if you want -only one of the link transactions to have scrips run. - -=cut - -Set($LinkTransactionsRun1Scrip, 0); - -=item C<$ResolveDefaultUpdateType> - -This option has been deprecated. You can configure this site-wide -with L</Lifecycles> (see L</Labeling and defining actions>). - -=back - =cut 1; |