Skip to main content

Global Settings

Global settings are only accessible to administrators via the administrator tab on the navigation bar. These settings change LOBSTA configuration for every user registered, and some even affect how LOBSTA is used. This section will not cover all available settings, but rather give a recommendation of the first settings one would change. For every other setting, check the global settings documentation.

General

These settings will highlight your firm´s name for any user exploring your application and distinguishing itself from other LOBSTAs.

SettingDefaultRecommendation
Application TitleBlankLOBSTA "Your Company Name"
Welcome textBlankFill
Hostname and pathBlankAutomatically fills from Application Title or can be manually changed.

Display

Display settings mostly focus on how the user views LOBSTA. Specifically, these settings change how time and language is displayed.

SettingDefaultRecommendation
Default LanguageJapaneseSelect the preferred company´s language.
Force default language for anonymous/ logged in usersBlankFill if users are monolingual. Leave blank if multilingual.
Time span format0.75Change to 0.45hr or keep at 0.75 depending on how you want to measure time.
Date/Time FormatBased on user´s languageLeave as is or change to a static format

Authentication

These settings cover application security regarding how users access the application and its contents, covering password strength, account registration, project visibility, two-factor authentication and session activity. Depending on your company's security policy, some of these settings might be in your best interest to manage

SettingDefaultRecommendation
Authentication requiredNo, allow anonymous access to public projectsChange to Yes so that only logged in users can view public projects.
Self-RegistrationManual account activationChange to Disabled so that only an admin can register a user.
Minimum password length8Increase for higher password security
Required character classes for passwordsBlankFill to increase password security
Require password change afterdisabledSelect a time period for passwords to require change.
Allow password reset via emailEnabledLeave Enabled
Two-Factor AuthenticationOptionalChange to disabled or required according to your security policy.
Session expirationdisabledSet a time period allowing a session to be on and timed out.

API

Projects

These settings change the defaults when creating new projects. A project´s author can access some of these settings in project settings, but not change the projects defaults.

SettingDefaultRecommendation
New projects are public by defaultCheckedUncheck to make projects private by default.
Default enabled modules for new projectsVariesCheck the modules that you want to be set as default. These can be unselected when making a project.
Default trackers for new projectsCheckedCheck the trackers that you want to be set as default. These can be unselected on project settings.
Role given to a non-admin user who creates a projectPlease SelectSelect a role to be automatically assigned to the author of the project.

Users

These settings limit the control users have over their accounts for security reasons. You can set email domains that are valid or invalid to be used to register to the application. Similarly, you can prevent a user from deleting their own account, making an admin the only one to be able to delete accounts.

SettingDefaultRecommendation
Dis/allowed email domainsBlankFill in with email domains your company trusts or distrusts.
Allow users to delete their own accountCheckedUncheck to prevent accidental account deletions.

Issue Tracking

These settings change how project issues are managed. Issue functionality that is changed here includes defining issue relations, subproject relation and percentage done on issues.

SettingDefaultRecommendation
Link issues on copyAskLeave as Ask, to set a copy relation when an issue is copied.
Close duplicate issues automaticallyCheckedAutomatically closes issues that LOBSTA detects as duplicates.
Allow issue assignment to groupsBlankCheck, as it allows groups to be assignees of issues.
Display subprojects on main projects by defaultCheckedUncheck to avoid cluttering of issues from project and subprojects.
Calculate the issue done ratio withUse the issue fieldLeave as is to allow manual input of % done or change to use the issue status to allow defining % done to issue status.
Parent task attributesCalculated from subtasksLeave as is to consider the subtasks attributes when calculating the parents attributes.

Time Tracking

These settings change time log configurations. You can select if certain fields are required to fill a log, as well as the maximum time required. Even time logs with 0 hours or on future dates can be accepted.

SettingDefaultRecommendation
Required fields for time logsBlankSelect Issues and Comment, so that these field are required to create a time log
Maximum hours that can be logged per day and user.999Set a maximum of hours that can be logged per day. Depending who has permission to fill time logs leaving at 999 is fine.
Accept time logs with 0 hoursCheckedLeave as is.
Accept time logs on future datesCheckedLeave as is.

Files

You can manage file settings, to limit the attachment size as well as limiting the extensions allowed to be submitted.

SettingDefaultRecommendation
Maximum attachment size51200KBIncrease or decrease according to the file size you expect to manage.
Dis/allowed extensionsBlankFill with extension your company trusts or manages.

Email notifications

These settings change how LOBSTA´s automatic email system work. You can change the address, and set under which circumstances users should be notified of changes. For these email messages, you can define both the header and footer all emails sent by the system will have.

SettingDefaultRecommendation
Emission email address[email protected]Set an identifiable address with your company´s name.
Show status changes in issue mail notifications subjectCheckedShows a status change on the email.
Actions for which email notifications should be sentVariesCheck the situations where an email notification should be sent to a user.
Email header/footerBlankWrite a header and a footer.