![]() ![]() If you provide a custom setting in both places, RT will issue a warning in the log as a reminder to consider removing the setting from etc/RT_SiteConfig.pm to avoid confusion. Any configuration options set there take precedence over values set in etc/RT_SiteConfig.pm. RT also allows you to set configuration via the RT web interface at Admin > Tools > System Configuration. More information about this option is available in the RT::Config documentation. If you have many customizations to manage, you can break your configuration into multiple files and put them in a directory etc/RT_SiteConfig.d/. The correct place to set site-specific options is in etc/RT_SiteConfig.pm. If you do, your changes will be lost when you upgrade and RT installs the newest version of this file on your system. You should never edit this file directly. This file, etc/RT_Config.pm, defines the available configuration options and sets the defaults for RT. The available options and valid values are described below. RT has dozens of configuration options to customize how RT behaves for different situations. Moving tickets between queues with different lifecycles.Statuses available during ticket creation.Transitions between statuses and UI actions.Syncing Users and Groups with LDAP or AD. ![]() External Authentication and Authorization.
0 Comments
Leave a Reply. |