Advanced settings

To change the advanced settings of the server, go to the Administration Panel and click Server Settings. This option is not available in the Desktop Client. Only the system administrator can change these settings.

The Regional Options and Formats groups of options are described in the section called “Regional settings”.

The Page Size groups of options allows you to specify the default number of issues displayed on a single page in the list of issues, and the default number of elements per page in the issue history. Each user can choose their own preferred settings using the User Preferences command. These options only affect the Web Client, because the Desktop Client always displays all issues and complete history without pagination.

Page Size
Figure 6.18. Page Size

Options from the View Settings group affect all users and all types of issues. When the Hide the ID column option is enabled, the ID column will not be displayed in the list of issues. When you hide the ID column, issues can still be sorted by this column, and the identifier of the selected issue will still be displayed in the Properties group in issue details view. When the Hide attributes with empty values option is enabled, attributes that don't have any value are not included in the issue details view. This option is usefult when issue types contain a lot of attributes, which are not always used.

You can select the order in which changes are displayed in the issue history view. Also it is possible to select the default filter in the issue history; you can display all history or just comments and attachments. Individual users may change these settings using the User Preferences command.

View Settings
Figure 6.19. View Settings

The Enable user registration option allows you to enable a module that allows users to register a new account. Additionally, you can enter an e-mail address to which notifications are sent about requests that are waiting for approval by the system administrator. They will be sent when there are new registration requests for approval, but not more often than once an hour. For more information about user registration, see the section called “Logging into the system” and the section called “Registration requests”.

User Registration
Figure 6.20. User Registration

Note

For the user registration module to work, you must properly configure the emails. Sending notifications with new registration requests also requires a working cron job. For more information, see the section called “Email notifications”.

Options from the Limits group allow the system administrator to specify the maximum length of comments and the maximum size of attachments that can be added by users.

Limits
Figure 6.21. Limits

Note

The maximum size of the attachment that can be sent to the system also depends on appropriate configuration of the web server and PHP. For more information, please visit http://php.net/manual/en/features.file-upload.common-pitfalls.php.

By default, small attachments are stored in the database, and large ones directly in the filesystem. Depending on your needs, you can change the threshold value or force storing all attachments only in the database or file system. The maximum size of attachments stored in the database can be specified in the Attachment Storage group.

Attachment Storage
Figure 6.22. Attachment Storage

Note

Storing large attachments in the database may require appropriate configuration of the database server, and can be less optimal compared to the file system. In addition, many hosting services significantly limit the maximum size of the database, while offering plenty of available disk space. On the other hand, storing attachments only in the database makes it easier to backup the system, since there is no need to backup additional files. In some cases it may also be safer.

Options from the Maximum Lifetime group allow you to define the time after which inactive user sessions are removed, and the maximum amount of time the entries in the Event Log and the user registration requests that are waiting for email address confirmation are stored by the system. The Garbage Collection setting determines the probability of running the clean up process, which removes inactive sessions, old entries in the Event Log and unconfirmed requests. Reduce the probability if the server is heavily loaded, or select Use cron job if the mechanism of sending email notifications is active (see the section called “Cron jobs”).

Maximum Lifetime & Garbage Collection
Figure 6.23. Maximum Lifetime & Garbage Collection