> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Board and Timeline
> The board is where Nextedy SCHEDULER lays scheduled work items out as bars against a grid of day columns, one group of rows per resource, inside a visible window you control.
export const LastReviewed = ({date}) => {
if (!date) return null;
const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
year: "numeric",
month: "long",
day: "numeric",
timeZone: "UTC"
});
return
Last reviewed on {formatted}
;
};
## What the Board Is Made Of
The Scheduler board has four parts, and every question about the timeline comes back to one of them.
| Part | Where it is | What it holds |
| ----------------- | ---------------- | -------------------------------------------------------------------------------------------- |
| Swimlane rows | Left-hand column | One group of rows per resource -- either a project user or an option of an enumeration field |
| Day columns | Across the top | One column per day, with a two-line header showing the month and the day number |
| Task bars | In the grid | One bar per scheduled work item, positioned on the days it runs |
| Unplanned sidebar | Right-hand side | Work items the query returned that are not scheduled yet |
Below the grid, the footer reports what is currently loaded: `Items loaded: N / Scheduled: M`, followed by `Timeline range:` and the first and last day of the window.
The rows themselves are the subject of [Swimlanes and Resources](/scheduler/concepts/swimlanes-and-resources); the coloured figures inside the grid are covered in [Capacity and Load](/scheduler/concepts/capacity-and-load).
## Two Views of the Same Data
The board renders in one of two layouts. The toolbar button **Toggle Resource Load visualization** switches between them, and it is active when you first open a board.
**The timeline view** is what you land on. Each resource contributes two stacked rows: a summary row whose day cells carry the per-day load markers, and a child row underneath that holds the task bars. Because the summary row is a folder, the pair can be collapsed and expanded.
**The flat view** appears when you turn Resource Load visualization off. Each resource becomes a single row of bars, the load markers are gone, and the row-folding controls no longer apply.
| | Timeline view (default) | Flat view |
| -------------------------------------- | -------------------------------------- | ----------------- |
| Rows per resource | A summary row plus a child row of bars | One row of bars |
| Per-day load markers | Yes, on the summary row | No |
| **Collapse rows** / **Expand rows** | Available | Greyed out |
| **Toggle Resource Load visualization** | Shown as active | Shown as inactive |
Collapsing every swimlane in the timeline view leaves only the summary rows, which turns the board into a pure capacity heatmap -- useful when you want to see who is over-committed without reading individual bars.
Your choice of view is remembered in your browser, together with the column width, so re-opening the page brings back the layout you left. See [Navigate the Timeline](/scheduler/guides/navigate-the-timeline) for the full set of view controls.
## Day Columns and Zoom
The x-axis is always days -- there is no week, month, or hour scale. Each column is 60 px wide by default, and the two zoom buttons change that width in steps of 30 px:
* **Zoom in the timeline** widens the columns, so fewer days are on screen and bars are easier to read.
* **Zoom out the timeline** narrows the columns, so more of the window fits on screen.
The width you settle on is remembered per user in the browser, so it survives a reload and applies the next time you open the board.
The current date is marked by a red line in the grid. **Scroll to today** brings that line back into view after you have scrolled away.
## Weekends and Non-Working Days
**Weekends are hidden by default.** The grid skips Saturday and Sunday entirely, so a Friday column is followed directly by the next Monday. The practical consequence is that the columns on screen are working days, not calendar days.
Other non-working days are handled differently: a day that a row's working calendar treats as non-working stays in the grid and is drawn with a diagonal hatch pattern. Hatched days carry no capacity, so they show no load figure.
Because weekends are skipped and off-days are hatched, the horizontal distance between two bars is a count of working days, not elapsed days. Durations behave the same way -- see [Dates, Duration and Effort](/scheduler/concepts/dates-duration-and-effort).
## The Visible Window
The board never shows an unbounded timeline. It renders a window anchored on today, defined by two parameters in the widget's **Advanced** panel:
| Parameter | Default | Effect |
| ---------------- | ------- | -------------------------------------------- |
| **Days Back** | `10` | How many days before today the window starts |
| **Days Forward** | `100` | How many days after today the window ends |
So a board with Days Back `10` and Days Forward `60` shows the range from ten days ago to sixty days ahead. The footer's `Timeline range` readout is the plain-language confirmation of that calculation: it prints the first and last day actually loaded.
Give **Days Forward** an explicit value. When it is left empty, its default is taken from the same project configuration property that supplies the **Days Back** default, which makes the forward reach of the board harder to predict. See [Advanced Configuration](/scheduler/guides/advanced-configuration).
Work items that the query returns but that carry no schedule are not drawn as bars at all. They wait in the **Unplanned** sidebar until you place them, which is what [Schedule and Reschedule Tasks](/scheduler/guides/schedule-and-reschedule-tasks) walks through.
## Reloading and Saving
**Refresh data** re-reads the work items from Polarion and redraws the board in place, which is what you use after someone else has changed dates or effort.
There is no Save control on the toolbar, and none is needed. Moving a bar, scheduling an item from the sidebar, or unplanning one writes straight back to the work item, so the board and Polarion stay in step without an explicit save step.
## See Also
* [Swimlanes and Resources](/scheduler/concepts/swimlanes-and-resources) -- where the rows come from and what capacity each kind of row carries
* [Capacity and Load](/scheduler/concepts/capacity-and-load) -- how to read the per-day load markers on the summary rows
* [Navigate the Timeline](/scheduler/guides/navigate-the-timeline) -- zoom, scroll, collapse, and view switching in practice
* [Toolbar Controls](/scheduler/reference/toolbar-controls) -- every toolbar button with its exact label and effect
* [Filter the Unplanned Sidebar](/scheduler/guides/filter-the-unplanned-sidebar) -- narrowing the backlog that feeds the board