> ## 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.

# Set Up a Release Gantt with Teams

> Configure a Nextedy GANTT chart that combines release planning with team assignments, allowing you to view work items filtered by both team and release using page parameters.

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 <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

## Prerequisites

* Team and Team Assignment work item types are configured (version 23.4.0+)
* A custom field of type **Enum > Nextedy Team** exists on both your Plan and work item types
* Separate Iterations (Plans) exist for each team

<Steps>
  <Step title="Create the Nextedy Team Custom Field">
    If you have not already created a team custom field, add one to both your Plan type and your work item type (such as Work Package):

    1. Navigate to **Administration > Work Items > Custom Fields**
    2. Create a field with type **Enum > Nextedy Team**
    3. Apply it to both the Plan and the relevant work item types

    The Nextedy Team enumeration automatically populates with all work items of type Team, letting you assign plans and tasks to specific teams.
  </Step>

  <Step title="Assign Teams to Iterations">
    For each Iteration (Plan), set the team custom field to the appropriate team:

    1. Open the Iteration in Polarion
    2. Select the matching team from the team custom field dropdown
    3. Ensure each team has its own set of Iterations for proper separation
  </Step>

  <Step title="Create Page Parameters">
    Set up two page parameters on your LiveDoc page to enable interactive filtering:

    | Page Parameter | Configuration                                                              |
    | -------------- | -------------------------------------------------------------------------- |
    | **Release**    | Points to the Plan/Release field, allowing selection of a specific release |
    | **Team**       | Points to the team custom field, allowing selection of a specific team     |

    <Tip title="Keep the Team Parameter ID as 'team'">
      When creating the Team page parameter, use `team` as the parameter ID. This specific naming is required for proper integration with the Gantt query field.
    </Tip>
  </Step>

  <Step title="Configure the Gantt Query">
    Connect the page parameters to the Gantt widget by setting the **Query Type** to **Lucene + Velocity** and entering a query such as:

    ```
    team.KEY:$pageParameters.team  #if($pageParameters.Release.singleValue())  AND PLAN:($pageParameters.Release) #end
    ```

    This query filters work items by the selected team and optionally by the selected release.
  </Step>

  <Step title="Add the Page Parameter Widget">
    Add the **Page Parameter** widget to the same LiveDoc page alongside the Gantt widget. This provides dropdown selectors for switching between teams and releases without editing widget parameters.
  </Step>

  <Step title="Add Iteration Markers (Optional)">
    To visually distinguish iteration boundaries on the Gantt chart, add a marker script in the **Markers Script** field of the widget parameters. The script queries plans matching the selected team and adds colored markers at each iteration due date.

    <Warning title="Update Project References in Scripts">
      If you use marker or item scripts, update the project ID references to match your actual Polarion project. Scripts referencing incorrect project IDs will fail silently and no markers will appear.
    </Warning>
  </Step>

  <Step title="Handle Unplanned Work Items (Optional)">
    If work items lack explicit start and end dates, you can use an item script to inherit the iteration dates. Add a script in the **Item Script** field that checks each work item for an assigned iteration and, if no dates are set, uses the iteration start and due dates as the task schedule.
  </Step>
</Steps>

## Understanding the Resource View

With this configuration, the resource view shows team members and their workload within the context of the selected team and release:

* **Team members** appear as resource rows with their assigned work items
* **Outside of Team** row appears when a work item is assigned to the selected team but the assignee is not a member of that team -- click to expand and see the specific user

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/Jklvz9qm2AdmIvBG/gantt/diagrams/guides/resources/release-gantt-with-teams/diagram-1.svg?fit=max&auto=format&n=Jklvz9qm2AdmIvBG&q=85&s=703e42aad6ab92d96bbb92d6c50266c4" alt="diagram" style={{ maxWidth: "480px", width: "100%" }} width="480" height="180" data-path="gantt/diagrams/guides/resources/release-gantt-with-teams/diagram-1.svg" />
</Frame>

## Verification

You should now see:

* Page parameter dropdowns for Team and Release on the LiveDoc page
* The Gantt chart filtering work items based on the selected team and release
* Resource view rows showing team member allocation for the filtered scope
* Iteration markers (if configured) highlighting plan boundaries

## See Also

* [Set Up Team Assignments Gantt](/gantt/guides/resources/team-assignments-gantt)
* [Set Up a Cross-Team Gantt Chart](/gantt/guides/resources/cross-team-gantt)
* [Configure Page Parameters](/gantt/guides/layout/page-parameters)
* [Use Dynamic Queries with Page Parameters](/gantt/guides/filtering/dynamic-queries)
* [Create Markers with Scripts](/gantt/guides/scripting/marker-scripts)

<LastReviewed date="2026-07-02" />