# FAQ / Troubleshooting

## General

<details>

<summary>Why are no issues showing in the Timeline?</summary>

Issues require both a **Start Date** and an **End Date** to appear on the Timeline. Check that:

1. The date fields are mapped correctly in [Field Mapping](/hiera-docs/admin-and-configuration/field-mapping.md).
2. Your issues have values in both date fields.
3. Use the [Table View](/hiera-docs/views-and-features/table-view.md) to identify issues missing dates.

</details>

<details>

<summary>What is the issue limit?</summary>

Hiera supports up to **10,000 issues** per project. Projects with more than 10,000 issues may experience slower load times or incomplete data. For very large projects, consider splitting work across multiple projects or using filters to reduce the visible scope.

</details>

<details>

<summary>Does Hiera work with Jira Standard?</summary>

Yes. Hiera is designed specifically for **Jira Standard** teams. It does not require Jira Premium or Advanced Roadmaps. Features like Strategic Parents provide hierarchy capabilities that are otherwise only available in higher Jira tiers.

</details>

## Configuration

<details>

<summary>I changed my hierarchy but the old structure still shows.</summary>

Hiera caches hierarchy data for performance. After changing the hierarchy configuration, **reload the page** to clear the cache and see the updated structure.

</details>

<details>

<summary>Field auto-detection did not find my custom fields.</summary>

Auto-detection matches common field names. If your fields use non-standard names, use the **manual mapping** option via the Fields button in the toolbar. See [Field Mapping](/hiera-docs/admin-and-configuration/field-mapping.md) for instructions.

</details>

## Performance

<details>

<summary>The first load is slow for large projects.</summary>

For projects with many issues (5,000+), the first load may take **10-15 seconds** as Hiera fetches and processes all issue data from Jira. Subsequent interactions are faster because the data is cached locally. If performance remains an issue, apply filters to reduce the number of visible items.

</details>

## Contact

If your question is not answered here, contact support:

* **Email**: <shv.support@germanmorales.org>
* **Response time**: 1-2 business days (CET/CEST)

See the [Support](/hiera-docs/support.md) page for details on what to include in your request.


---

# 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/faq-troubleshooting.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.