Board and Timeline
The two views of the board, the day-column grid and its month/day header, zoom, hidden weekends, and the timeline window behind “Timeline range”.
Swimlanes and Resources
What a row is: project users in assignee mode, or the options of an enumeration field — and the read-only Time Points row.
Capacity and Load
How per-day load markers are calculated from effort, the capacity each kind of row carries, and the four colour bands up to and beyond 100%.
Dates, Duration and Effort
The Data Mapping of Start, End and Duration fields, the three scheduling modes it produces, and how Plans Type decides which effort a card shows.
Dependencies
Dependency Roles, why board links are ordinary Polarion work-item links, and when the arrows between bars are drawn.
How the concepts fit together
The board is a grid of days across resources: Board and Timeline defines the columns, Swimlanes and Resources defines the rows. A work item becomes a bar in that grid through Dates, Duration and Effort — the mapped date fields place it, the mapped duration or effort gives it length. The same effort then feeds Capacity and Load, which compares the hours booked per row per day against that row’s capacity and colours the day accordingly. Dependencies adds the one relationship the grid itself cannot express: which task waits for which. Because all four inputs are work-item fields, the board never holds state of its own — anything you change by dragging is written straight back to Polarion, and anything changed in Polarion shows up on the board on the next load or after Refresh data.Each concept has a matching set of widget parameters — swimlane mode, Data Mapping, Plans Type, Dependency Roles, and the timeline window. Widget Parameters lists them all with their defaults, and Add the Scheduler Widget shows where to set them.