Skip to main content
Resource View panel showing per-user workload allocation rows below the Gantt chart
The Resource View adds a grid below the Gantt timeline with one row per resource. Cell values indicate the effort assigned to each user, and hovering over a load cell reveals a tooltip with work item IDs or capacity details.
Resource View cells with effort values per user and time period
Tooltip on a Resource View load cell showing work item IDs and capacity detail
1

Enable the Resource View

  1. Open the Gantt page in Edit mode.
  2. Click the widget gear icon to open Widget Parameters.
  3. In the Resource View section, set Show Resource View to Yes.
  4. Click Apply.
Once enabled, additional parameters appear in the Resource View section.
Resource View parameters in the Gantt Widget Parameters panel
Resource view sub-parameters such as View Height, Resource Field, and Resource Load Calculation only become visible after you set Show Resource View to Yes.
2

Configure Resource View Parameters

3

Choose a Resource Load Calculation Mode

The Gantt offers four calculation modes for the resource view cells:
Resource Load Calculation dropdown listing the four available calculation modes
Leaf Items Count counts each leaf-level item as one unit. In the example below, the two leaf items each contribute a green cell marked “1” for their scheduled timeframe.
Leaf Items Count mode showing green cells marked 1 for each leaf-level work item
Estimate + Spent combines remaining estimate with time already spent and distributes it across the scheduled days, making it easy to spot overloaded team members.
Estimate plus Spent mode showing combined effort distributed across days
When 96 hours of combined effort are spread across 10 scheduled days, the Resource View shows a daily load of 9.6 hours for the assigned user.
Resource View cell showing 9.6 hours per day from 96 hours over 10 days
Remaining Estimate distributes only the future remaining effort across scheduled days. A 6-day remaining estimate spread across 10 calendar days yields a workload of 4.8 hours per day.
Remaining Estimate mode showing 4.8 hours per day from a 6-day estimate over 10 days
Assignment Allocation shows percentage-based team allocation. A user assigned 35% in one team and 10% in another shows a combined 45% workload for that period; totals above 100% indicate overallocation.
Assignment Allocation mode showing a combined 45 percent workload across two teams
If your project tracks time spent, the Remaining Estimate mode gives you the most actionable view of outstanding work without inflating numbers with already-completed effort.
The resource load calculation considers work item resolution status, not just time fields. If a work item is resolved, it may be excluded from certain calculation modes. Use Remaining Estimate mode if resolved items appear to inflate numbers in Estimate + Spent mode.
Split the effort between multiple assignees. By default, a task’s effort is shown in full for every assignee — a 4-day estimate appears as 4 days for each one.
Task effort shown in full for each of its multiple assignees by default
To divide the effort equally between assignees instead, add nextedy.gantt.multiAssignmentSameEffortForAll=false to Administration > Configuration Properties.
Resource View with task effort split equally between multiple assignees
4

Show Unassigned Work Items

To see work items that have no resource assigned:
  1. Set Show Unassigned to Yes in the Resource View parameters.
  2. A dedicated row labeled “Unassigned” appears at the bottom of the resource view.
This helps you identify unallocated tasks during sprint or release planning.Show only users with tasks assigned. Starting with version 24.1.1, the Hide No Task Resources button on the Gantt toolbar lets you collapse the list to resources that actually carry work. By default, all resources are shown.
Hide No Task Resources button on the Gantt toolbar
Resource View with all resources shown, including those without tasks
Toggling the button hides every resource that has no tasks from the Gantt page.
Resource View with task-less resources hidden after toggling Hide No Task Resources
5

Adjust the View Height

You can set the initial panel height via the View Height parameter. After the Gantt loads, you can also resize the resource view by dragging the horizontal divider between the Gantt chart and the resource view.
6

Customize Marker Colors

Resource allocation markers use color coding to indicate capacity status:
  • Green cells indicate the resource is within capacity
  • Red cells indicate the resource is overallocated
The default scheme uses green for acceptable allocation and red for overallocation.
Default green and red allocation bubbles in the Resource View
You can customize these bubbles for a clearer, more intuitive allocation overview.
Resource View with customized allocation bubble colors
With the dynamic approach, you define color thresholds via the Gantt Config Script or Configuration Properties — for example, lightgreen up to 50%, #51c185 up to 100%, orange up to 150%, and #ff8686 above 150%.
Resource View bubbles colored by allocation thresholds defined in the config script
Team overallocation color schemes let you distinguish global overload from in-team overload. Since version 25.4.1, this also works when defined via Configuration Properties at project or global level.
Team overallocation color scheme distinguishing global overload from in-team overload
Example Resource View with global and in-team overload colors applied
With the static approach, a Script Block widget overrides the OK marker (default green bubble) and the overloaded marker (default red bubble) so you can apply any background-color and color combination.
The static CSS approach applies to Leaf Items Count and Assignment Allocation modes. For Estimate + Spent and Remaining Estimate modes, use the dynamic resourceMarkersColorConfig approach instead.
Resource View with allocation markers restyled via a static Script Block widget
For full instructions, see Configure Resource Allocation Marker Colors.
When using Leaf Items Count mode, only leaf-level work items (those with no children) are counted. If you enable onlyLeafTasks, parent summary tasks are excluded from both the Gantt display and resource calculations.
Only Tasks and Work Packages that have no child items are counted as load for their assignees, so real, hands-on work is counted once per user and parent items are not double-counted.
Resource load counting only leaf-level Tasks and Work Packages, not parent items
To count higher-level items as well — useful when you intentionally track effort at multiple levels — set nextedy.gantt.config.onlyLeafTasks=false in Widget Properties > Gantt Config Script.
Gantt Config Script with onlyLeafTasks set to false to count all items
With that setting, all items are counted in the Resource View.
Resource View counting all items, including parent-level items
To skip specific tasks from the calculation — for example, keeping only Work Packages — add a rule to the Item Script such as if(wi.getType().getId()==="task") { task.load=0; }.
Item Script setting task load to zero to exclude tasks from the Resource load
You can also calculate Resource Load globally while showing only the project timeline, so the load counts items from other projects too.
Project timeline shown while Resource Load is calculated across multiple projects
Achieve this by querying items from multiple projects.
Query configuration pulling work items from multiple projects for global Resource Load

Verification

You should now see:
  • A resource view panel below the Gantt chart with one row per assigned resource
  • Workload values in each cell matching your chosen calculation mode
  • Color-coded cells indicating within-capacity (green) and overallocation (red) states

See Also

Last modified on July 10, 2026