General settings

The General Settings section allows administrators to manage foundational preferences that affect the overall functionality of the TimePlanner app.

Here’s an overview of the options available:

Settings	How does it work?
Allow user to change default approver	If this setting is ON, the users can change the default Leave & Timesheet approver in “My settings”.
Allow users to change capacity	If this setting is ON, the user can change his/her own daily capacity scheme in “My settings”.
Allow users to change the calendar	If this setting is ON, the user can change his/her holiday calendar in “My settings”.
Allow users to add him/herself as timesheet/vacation approver	If this setting is ON the user can add him/herself as a timesheet/vacation approver in “My settings” Note: Users must have timesheet/vacation approval permissions. To grant these permissions, please configure them in the Permission Settings.
Allow users to set billable for a task	This setting allows normal users can mark tasks as billable.
Sync Jira worklogs	TeamBoard only allows to sync seamlessly with Jira worklog, and this setting can not be disabled.
Sync with Jira estimation fields	When this setting is enabled, the schedule will automatically sync with the Original Estimate and Time Remaining fields in Jira.
Plan with Original Estimation field	MAPPING PROJECT Task hours per day will be calculated by dividing the Original Estimate by the task's duration. Changing start date or end date will not affect Original Estimate value. Given an example, user A is assigned with task 01: Original Estimate is 10h Start date is 19th February End date is 20th February → task hours/day will be 5h/day
Prevent planning tasks on holiday	If this setting is ON, the system will automatically exclude the scheduled hours of task for those days. If this setting is OFF, the system will include the scheduled hours of task for those days.
Enable calculation undertime by-date	This feature calculates undertime by comparing daily logged hours against the standard capacity. Given an example, user A has 8h/day capacity and works in 3 days: Day 1: log 8h Day 2: log 5h Day 3: log 11h → user A is undertime 3h compared to capacity ( Day 2) and logged 3h more on day 3. → Overall, user A meets total expected logged hour against capacity for the period.