# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.

Template: request-tracker3.8/rtname
Type: string
_Description: Name for this Request Tracker (RT) instance:
 Every installation of Request Tracker must have a unique name.
 The domain name or an abbreviation of the organization name are
 usually good candidates.
 .
 Please note that once you start using a name, you should probably never
 change it. Otherwise, mail for existing tickets won't get put in the right
 place.
 .
 This setting corresponds to the $rtname configuration variable.

Template: request-tracker3.8/organization
Type: string
_Description: Identifier for this RT instance:
 In addition to its name, every installation of Request Tracker must also have
 a unique identifier. It is used when linking between RT installations.
 .
 Using this machine's fully qualified hostname (including the DNS domain name)
 is recommended.
 .
 This setting corresponds to the $Organization configuration variable.

Template: request-tracker3.8/correspondaddress
Type: string
_Description: Default email address for RT correspondence:
 Please choose the address that will be listed in From: and Reply-To: headers of
 emails tracked by RT, unless overridden by a queue-specific
 address.
 .
 This setting corresponds to the $CorrespondAddress configuration variable.

Template: request-tracker3.8/commentaddress
Type: string
_Description: Default email address for RT comments:
 Please choose the address that will be listed in From: and Reply-To: headers of comment
 emails, unless overridden by a queue-specific address. Comments can be
 used for adding ticket information that is not visible to the client.
 .
 This setting corresponds to the $CommentAddress configuration variable.

Template: request-tracker3.8/webbaseurl
Type: string
_Description: Base URL for the RT web interface:
 Please specify the scheme, server and (optionally) port for constructing
 RT web interface URLs.
 .
 The value should not have a trailing slash (/).
 .
 This setting corresponds to the $WebBaseURL configuration variable.

Template: request-tracker3.8/webpath
Type: string
_Description: Path to the RT web interface:
 If the RT web interface is going to be installed somewhere other than at
 the documents root of the web server, you should specify the path to it here.
 .
 The value requires a leading slash (/) but not a trailing one.
 .
 This setting corresponds to the $WebPath configuration variable.

Template: request-tracker3.8/handle-siteconfig-permissions
Type: boolean
_Description: Handle RT_SiteConfig.pm permissions?
 The RT web interface needs access to the database password, stored in the
 main RT configuration file. Because of this, the file is made readable by
 the www-data group in normal setups. This may have security implications.
 .
 If you reject this option, the file will be readable only by root, and
 you will have to set up appropriate access controls yourself.
 .
 With the SQLite backend, this choice will also affect the
 permissions of automatically-generated local database files.

Template: request-tracker3.8/warn-sqlite-file
Type: error
_Description: Broken SQLite file
 Due to a bug in earlier versions of this package, the RT database has been
 placed in /var/lib/dbconfig-common/sqlite3/request-tracker3.8/_DBC_DBNAME_
 rather than its intended location.
 .
 After this installation completes, you
 will need to manually move the file to its correct location
 (see /etc/request-tracker3.8/RT_SiteConfig.d/51-dbconfig-common). RT will
 not work until this action is taken.
