Page tree

Documentation for Structure.Gantt version 2.3 and patch releases. Version Index | ALM Works Business Continuity During the COVID-19 Outbreak

Skip to end of metadata
Go to start of metadata

In the Resources section of the Gantt configuration you can configure the way resources are assigned to tasks and the default settings for resources.

This article covers resource assignment and setting default values for resources and tasks. To learn more about managing resources within your Gantt chart, see Resource Management.

Resource Assignment

You can assign resources to issues using a Jira field (including text, list and user fields) or a Structure attribute, such as a value calculated through Formulas.

Here are a few common examples of resource assignments:

  • To use each task's assigned user as its resource, select Assignee.
  • To use teams as resources, create a text custom field called "Teams" and populate it with team names accordingly. Structure.Gantt will automatically merge similar values.
  • You can also combine these using a simple formula: "Assignee OR Team". If there is an Assignee for an issue, Structure will use that field. Otherwise, it will use the Team. (If you want to default to Team instead, switch the order of your formula: "Team OR Assignee".

By default, "None" value is selected.

When no attribute is chosen (or there is no value for that attribute field), a "default" resource is used with default settings. This does not appear in your Resources chart, but it is listed on the Task Details Panel:

Default Resource Settings

In order to correctly allocate resources and place that information within your Gantt and Resource Usage charts, Structure.Gantt needs to determine the following parameters for each resource:

  • Units - Defines the "size" of a resource. By default, the value is 1, which corresponds to 1 person. If you use teams as resources, and each team has 5 people able to use all available time to work on tasks, you would enter 5.
  • Time Zone - Defines the default time zone of the resources.
  • Work Calendar - Defines the default working and non-working hours for the resource.


Default values will be used when a resource does not have its own values specified or when no resource is provided. These values can be overwritten for individual resources, through Resource Settings. See Resource Management for more information.

Task Settings

Task settings allow you to configure Maximum Units and Leveling Priority.

Max. Units Attribute

Maximum Units defines the maximum number of resource units that can be allocated for a task. For example, if you set the default Resource Units (above) to 5 and the Maximum Units for a task to 1, that task won't be able to use more than 1/5 of a resource's capacity.

Max. Units Attribute allows you to select where the Maximum Units values are stored. You can choose a Jira field, Structure attribute or the Structure.Gantt database. Once selected, the Maximum Units value for each task can be set or updated using the Task Details panel (see Gantt Chart Elements). If a Jira field or Structure attribute is used, you can also update the maximum units for a task directly in your structure, by adding the appropriate column to your view.

Default Max. Units

This default value will be used when a task does not already have a maximum units value set.

Leveling Priority

Leveling Priority allows you to prioritize certain tasks when using the Resource Leveling feature in Structure.Gantt. When tasks need to be moved due to overallocation, those with higher weights will be placed earlier in the timeline.

By default, internal storage is used for Leveling Priority, all tasks are given the Default Leveling Priority and a new priority can be set for individual tasks using the Task Details PanelLeveling Priority can also be automatically assigned to tasks based on a standard attribute, custom field or formula. Additionally, these settings can be customized for specific issues using Slices.

The Default Leveling Priority value is used for tasks when no other value is specified.

  • No labels