> For the complete documentation index, see [llms.txt](https://hiera.gitbook.io/hiera-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hiera.gitbook.io/hiera-docs/getting-started.md).

# Getting Started

This guide walks you through installing Hiera, completing your first configuration, and taking a quick tour of the project views and global Workload view.

### Installation

1. Visit the [Hiera listing on Atlassian Marketplace](https://marketplace.atlassian.com/apps/1914332338).
2. Start the installation or trial and select the Jira Cloud site where you want to install the app.
3. Confirm the permissions. Hiera is built on Atlassian Forge and declares no external fetch permissions.
4. Once installed, open Hiera from a Jira project's sidebar. For cross-project views, open the global Hiera page from Jira's Apps menu.

### First Configuration

After installation, Hiera can load using Jira metadata and automatically detected fields. Review these two project-level settings before relying on the planning views:

#### 1. Hierarchy Configuration

The setup wizard suggests levels from the issue types and hierarchy metadata available in the current project. Review, add, remove, group, or reorder them to match your project structure.

* Open Hiera in a project and click the **Hierarchy** button in the toolbar.
* Add, remove, or reorder issue types to match your project structure.
* Click **Save** to store the configuration.

See Hierarchy Setup for full details.

#### 2. Field Mapping

Hiera maps standard and custom fields for dates, teams, risk, and more. It auto-detects common field names, but you may need to adjust mappings manually.

* Click the **Fields** button in the toolbar.
* Verify or set mappings for: Start date, End date, Area / Cluster, Team / Subteam, Progress, Risk, Impact, Estimation, Planning period, and Timeline color.
* Select **Save mapping**.

See Field Mapping for full details.

### Quick Tour of Views

Hiera has seven in-project tabs. The global Hiera page, opened from Jira's Apps menu, separately provides Projects, Capacity, Workload, and Cost tabs. The table below summarizes the seven project tabs and the global Workload view.

| View             | Purpose                                                                                                                                     |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Timeline**     | Gantt chart with hierarchical tree, drag-and-drop scheduling, dependency overlays, and export options                                       |
| **Dependencies** | Interactive dependency map with focused inspection, grouping, contextual legend, conflict detection, and a navigable critical-path estimate |
| **Risk Matrix**  | 3x3 grid plotting issues by Risk and Impact, with KPI summary cards                                                                         |
| **Table View**   | Flat dependency summary with Key, Summary, Type, Status, Area, Blocks, and Blocked By columns                                               |
| **Capacity**     | Weekly issue-count heatmap grouped by assignee, team, or area                                                                               |
| **Workload**     | Cross-project planning matrix for hours allocation, plan vs. actual tracking                                                                |
| **OKR View**     | Tree view of objectives with child-completion rollups and each item's Jira status                                                           |
| **Portfolio**    | Card grid of top-level items with Jira status, completion progress, and child counts                                                        |

Shared Search, Status, Owner, and configurable filter slots affect the current project view. Timeline and Dependencies also provide controls specific to those views.

In the Timeline, select the **Plan Quality** metric to open a weighted planning-quality view. It reports coverage for dates, owners, estimates, risk assessments, hierarchy, and dependencies, with alerts for missing planning data, overdue work, dependency conflicts, and orphaned items.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://hiera.gitbook.io/hiera-docs/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.