Understanding the Plan Hierarchy
A typical multi-level setup looks like this:1
Configure the Plans Dataset
Open Widget Parameters > Plans Dataset and set up a dataset filter to select the top-level plans. For example, filter by template to show only Release plans:
- Set the Plans dataset to show plans with Template: Release
2
Set the Load Children Depth
Navigate to Widget Parameters > Load Children and set the number of sub-plan levels to load:
For a typical Release > Iteration > Work Package structure, set Load Children to
2 or 3.3
Configure Plan Types
In the Plan Types Configurations section of the widget parameters, define which plan template types you use and their hierarchy:
- Add each plan type (e.g., Release, Iteration)
- For each child type, specify which plan types are allowed as parents
- Plans do not use dependency link roles — only parent-child relationships apply
4
Enable Work Items Under Plans
To show work items beneath their parent plans, scroll to the Show Plan Work Item section:
- Set Enable Show Items to
Yes - Configure the Data Mapping fields:
- Start Field — the work item field used for task start dates
- End Field — the work item field used for task end dates
- Duration Field — the work item field for duration
- Progress Field — the work item field for completion percentage
- Parent Role — the link role defining parent-child relationships between work items
- Dependency Role — the link role for dependency links between work items
5
Configure Work Item Types
In the Work Item Types Configuration section, add entries for each work item type that should appear under plans:
- Set the Item Type for each type (e.g., Work Package, Task)
- Configure the Gantt Presentation Mode (Item, Derived Schedule, Milestone, or Auto-Mode)
- Set Parent Mode to control hierarchy placement