# Capacity

The Capacity view displays a heatmap of workload distribution across assignees or teams over time. It helps you identify overallocation and balance work before it becomes a bottleneck.

## Prerequisites

The Capacity view requires issues to have **Start Date** and **End Date** values. Issues without dates are excluded from the heatmap. Ensure these fields are mapped in [Field Mapping](file:///1698742/admin-and-configuration/field-mapping.md).

## Heatmap Display

The heatmap uses a color scale to indicate load levels:

* **Green** -- normal load; the assignee or team has capacity available
* **Yellow** -- approaching full capacity
* **Red** -- overloaded; more work is assigned than available capacity for that period

Each cell in the heatmap represents a time period (day, week, or month depending on zoom level) for a specific assignee or team.

## Grouping

You can group the heatmap rows by:

* **Assignee** -- one row per person, showing their individual workload over time
* **Team** -- one row per team, aggregating all members' workload

Switch between groupings using the selector in the toolbar.

## Reading the Heatmap

Hover over any cell to see the detail breakdown:

* Number of issues assigned in that period
* Total story points or estimated hours
* List of specific issues contributing to the load

## Filters

All toolbar filters apply. This allows you to focus capacity analysis on specific areas, teams, statuses, or time ranges.

## Practical Tips

* Use the Capacity view at the start of each sprint or quarter to detect overallocation early.
* Combine with the Timeline view to reschedule items and rebalance load.
* Switch between Assignee and Team groupings to get both individual and aggregate perspectives.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hiera.gitbook.io/hiera-docs/views-and-features/capacity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.