Import Calendars from CSV

​

Prerequisites

• Access to the Polarion server file system (to place the CSV file)
• Access to Administration > Configuration Properties

1

Prepare the CSV File

Create a semicolon-delimited CSV file with the following column order:

Column	Description	Example
PROJECT_ID	Polarion project ID	MyProject
USER_ID	Polarion user ID	jsmith
YEAR	Calendar year	2025
START	Start day of year (1-366)	60
END	End day of year (1-366)	90
CAPACITY	Working hours per day	8

Each row defines a capacity period for one user. Set CAPACITY to 0 for non-working periods.

The START and END columns use day-of-year numbers (1 = January 1; December 31 is day 365, or day 366 in a leap year). You can calculate these from dates in a spreadsheet before exporting.

2

Upload the CSV File

Place the file at the following path on the Polarion server:

/.polarion/nextedy/resource-capacity.csv

This is the fixed path that the Gantt reads from. The file must be accessible to the Polarion server process.

3

Enable CSV Calendar Loading

Add the following property under Administration > Configuration Properties:

nextedy.gantt.loadResourcesFromCsv=true

This tells the Gantt to load resource definitions from the CSV file instead of from Polarion users.

When the CSV file is being parsed for the first time, the Gantt widget displays a message: “CSV User Calendar is loading, it may take few minutes…”. This is expected behavior during the initial load.

4

Enable Working Calendars in the Widget

Open the Gantt widget parameters and navigate to Working Calendars:

1. Set Use Working Calendar to Yes
2. Set Load User Calendars to Yes

5

Enable Calendar Caching (Recommended)

For improved performance on repeated page loads, enable server-side caching:

nextedy.gantt.workingCalendar.useCache=true

The cache persists between page loads. After updating the CSV file, clear the cache to load the new data.

After replacing the CSV file, you must clear the calendar cache for changes to take effect. Use the Clear Calendar Cache toolbar button (shown when caching is enabled) or the api/clearCalendarCache endpoint.

​

CSV File Example

MyProject;jsmith;2025;1;120;8
MyProject;jsmith;2025;121;125;0
MyProject;jsmith;2025;126;365;8
MyProject;mdoe;2025;1;365;6

• jsmith works 8 hours per day, except days 121-125 (a vacation week with 0 hours)
• mdoe works 6 hours per day all year

​

Verify

​

See Also

• Set Up Work Item Calendars
• Use Calendars from Another Project
• Customize Working Hours per Resource
• Set Up the Resource View