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.

Setting	Default	Recommendation
Application Title	Blank	LOBSTA "Your Company Name"
Welcome text	Blank	Fill
Hostname and path	Blank	Automatically 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.

Setting	Default	Recommendation
Default Language	Japanese	Select the preferred company´s language.
Force default language for anonymous/ logged in users	Blank	Fill if users are monolingual. Leave blank if multilingual.
Time span format	0.75	Change to 0.45hr or keep at 0.75 depending on how you want to measure time.
Date/Time Format	Based on user´s language	Leave 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

Setting	Default	Recommendation
Authentication required	No, allow anonymous access to public projects	Change to Yes so that only logged in users can view public projects.
Self-Registration	Manual account activation	Change to Disabled so that only an admin can register a user.
Minimum password length	8	Increase for higher password security
Required character classes for passwords	Blank	Fill to increase password security
Require password change after	disabled	Select a time period for passwords to require change.
Allow password reset via email	Enabled	Leave Enabled
Two-Factor Authentication	Optional	Change to disabled or required according to your security policy.
Session expiration	disabled	Set 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.

Setting	Default	Recommendation
New projects are public by default	Checked	Uncheck to make projects private by default.
Default enabled modules for new projects	Varies	Check the modules that you want to be set as default. These can be unselected when making a project.
Default trackers for new projects	Checked	Check 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 project	Please Select	Select 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.

Setting	Default	Recommendation
Dis/allowed email domains	Blank	Fill in with email domains your company trusts or distrusts.
Allow users to delete their own account	Checked	Uncheck 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.

Setting	Default	Recommendation
Link issues on copy	Ask	Leave as Ask, to set a copy relation when an issue is copied.
Close duplicate issues automatically	Checked	Automatically closes issues that LOBSTA detects as duplicates.
Allow issue assignment to groups	Blank	Check, as it allows groups to be assignees of issues.
Display subprojects on main projects by default	Checked	Uncheck to avoid cluttering of issues from project and subprojects.
Calculate the issue done ratio with	Use the issue field	Leave as is to allow manual input of % done or change to use the issue status to allow defining % done to issue status.
Parent task attributes	Calculated from subtasks	Leave 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.

Setting	Default	Recommendation
Required fields for time logs	Blank	Select Issues and Comment, so that these field are required to create a time log
Maximum hours that can be logged per day and user.	999	Set 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 hours	Checked	Leave as is.
Accept time logs on future dates	Checked	Leave as is.

Files

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

Setting	Default	Recommendation
Maximum attachment size	51200KB	Increase or decrease according to the file size you expect to manage.
Dis/allowed extensions	Blank	Fill 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.

Setting	Default	Recommendation
Emission email address	[email protected]	Set an identifiable address with your company´s name.
Show status changes in issue mail notifications subject	Checked	Shows a status change on the email.
Actions for which email notifications should be sent	Varies	Check the situations where an email notification should be sent to a user.
Email header/footer	Blank	Write a header and a footer.