# Portfolio

The Portfolio view presents a card grid of your top-level items, giving you a high-level overview of initiatives, epics, or strategic parents across the project.

## Card Grid

Each card represents a top-level item in your hierarchy and displays:

* **Issue key and summary**
* **Status** -- current workflow status with color-coded badge
* **Health** -- derived from date compliance and blocker status of child items
* **Child count** -- number of direct children and their aggregate completion

Cards are arranged in a responsive grid that adjusts to your screen size.

## Interaction

Click on any card to open the **detail panel** on the right side of the screen. The detail panel shows:

* Full issue details (type, status, assignee, dates, description)
* Child items with their statuses
* Dependencies
* Strategic Parent assignment (if applicable)

From the detail panel, you can navigate directly to the issue in Jira or update fields inline.

## Toolbar Filters

The Portfolio view respects all toolbar filters:

* **Text search** -- filter cards by key or summary
* **Status** -- show only cards matching specific statuses
* **Assignee** -- filter by owner
* **Area / Team** -- focus on a specific area or team
* **Quarter** -- show items relevant to a specific quarter
* **Labels** -- filter by Jira labels
* **Risk-only** -- show only items with risk data

## When to Use Portfolio View

* **Executive reviews** -- quickly scan the health and status of all major initiatives
* **Planning sessions** -- identify which top-level items need attention
* **Status reporting** -- get a visual summary without diving into individual timelines

The Portfolio view pairs well with the OKR View for organizations that align initiatives to objectives.


---

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