Calendar and Working Hours Properties

Set these properties in Administration > Configuration Properties.

Calendar Project Properties

Name	Type	Default	Description
`nextedy.gantt.workitemCalendar.projectId`	`String`	empty	Polarion project ID where work item calendars (per-user and global) are stored. Must be set on both the calendar project and any projects that reference it.
`nextedy.gantt.workitemCalendar.globalID`	`String`	empty	Work item ID of a `calendar` type work item used as the global calendar. If you prefer not to create a dedicated calendar, you can use a placeholder empty calendar.
`nextedy.gantt.calendarHolder`	`String`	empty	Polarion user ID whose calendar work item is used as the global working calendar. Use this when the global calendar is assigned to a specific user account rather than being project-level.

The nextedy.gantt.workitemCalendar.projectId and nextedy.gantt.workitemCalendar.globalID properties must be configured on both the calendar project and any consuming projects.

Working Hours Properties

Name	Type	Default	Description
`nextedy.gantt.workingHoursPerDay`	`Integer`	`8`	Default number of working hours per day for all resources. Set in Administration > Configuration Properties to apply globally, or override per widget via Gantt Config Script.

Custom Working Hours Function

For different working hours per resource, define a custom function in the Gantt Config Script widget parameter:

gantt.config.workingHoursPerDayFunction = (resource) => {
  if (resource === "rProject") {
    return 4;
  }
  return 8;
};

The Gantt Config Script supports Velocity expressions. You can use $trackerService to dynamically build the working hours function based on work item data. The function definition is produced by Velocity on the server, then executed on the client.

Calendar Work Item Types

The working calendar system uses four dedicated work item types:

Work Item Type	ID	Purpose
Calendar	`calendar`	Defines regular working hours per weekday and the validity date range. All exceptions and inheritance chains connect to this type.
Time Off	`timeoff`	Marks specific date ranges as non-working days in a linked calendar. Used for holidays and vacations.
Time On	`timeon`	Activates additional working days, overriding Time Off exceptions. Used when a specific user must work during a global holiday.
Tweak	`scheduletweak`	Adjusts working hours for a date range without changing working/non-working status. Used for half-days or reduced schedules.

Calendar Custom Fields

Each calendar work item uses the following custom fields to define the weekly schedule:

Field	Type	Format	Description
`from`	Date	`YYYY-MM-DD`	Date when the calendar becomes active. If empty, no start boundary.
`to`	Date	`YYYY-MM-DD`	Date when the calendar expires. If empty, no end boundary.
`regularMonday`	`String`	`HH:mm,HH:mm`	Working hours for Monday. Use `-` for explicitly non-working. Leave empty to inherit from parent calendar.
`regularTuesday`	`String`	`HH:mm,HH:mm`	Working hours for Tuesday. Same format as Monday.
`regularWednesday`	`String`	`HH:mm,HH:mm`	Working hours for Wednesday. Same format as Monday.
`regularThursday`	`String`	`HH:mm,HH:mm`	Working hours for Thursday. Same format as Monday.
`regularFriday`	`String`	`HH:mm,HH:mm`	Working hours for Friday. Same format as Monday.
`regularSaturday`	`String`	`HH:mm,HH:mm`	Working hours for Saturday. Typically `-` for standard work week.
`regularSunday`	`String`	`HH:mm,HH:mm`	Working hours for Sunday. Typically `-` for standard work week.

Use the format HH:mm,HH:mm (e.g., 09:00,17:00 for a standard 8-hour day). Use - to mark a day as explicitly non-working. Leave the field empty to inherit hours from the parent calendar.

Calendar Inheritance

Calendars support inheritance via the inherits from work item link role:

A child calendar inherits base hours from its parent calendar
Weekday fields left empty in the child calendar use the parent’s hours
Weekday fields set explicitly in the child override the parent’s hours
The - value means explicitly non-working (does not inherit)

Resolution Order

When the Gantt chart calculates effective working hours for a specific date, it applies the following resolution order:

Calendar Modes in Resource View

The resource view supports three calendar resolution modes that affect capacity calculation:

Mode	Description
Global Calendar	Default mode. Uses the project-wide working calendar for all resources. Off-days apply to all task and resource rows equally.
User Calendars	When Load User Calendars is enabled, per-user working calendars are applied per resource row. Each user’s off-days are based on their individual calendar.
Team Assignments	When Load Team Assignments is enabled, cells where a resource has zero team assignment hours are marked as unavailable.

A designated user can act as a base calendar holder (via nextedy.gantt.calendarHolder). Their off-days are applied as the baseline, and other users’ calendars overlay additional off-days on top.

Configuration Example

To connect a project to a central working calendar project:

nextedy.gantt.workitemCalendar.projectId=WICalendars
nextedy.gantt.workitemCalendar.globalID=WI-001

To set a global calendar via a placeholder user:

nextedy.gantt.calendarHolder=calendarUser

To change the default working hours globally:

nextedy.gantt.workingHoursPerDay=7

Working Calendars Parameters — widget-level calendar settings
Team and Resource Properties — team capacity and resource configuration
Resource View Parameters — resource load modes and display options
Item Script API — access calendar data in scripts

​Calendar Project Properties

​Working Hours Properties

​Custom Working Hours Function

​Calendar Work Item Types

​Calendar Custom Fields

​Calendar Inheritance

​Resolution Order

​Calendar Modes in Resource View

​Configuration Example

​Related Pages

Calendar Project Properties

Working Hours Properties

Custom Working Hours Function

Calendar Work Item Types

Calendar Custom Fields

Calendar Inheritance

Resolution Order

Calendar Modes in Resource View

Configuration Example

Related Pages