# Release Notes

## v7.1.0 -- May 19, 2026

### New Features

* **Strategic Parents** -- a new hierarchy level above Epics for Jira Standard teams. Group Epics under strategic themes or programs without requiring Jira Premium. See [Strategic Parents](/hiera-docs/strategic-parents.md).
* **Detail Panel Picker** -- assign and change Strategic Parents directly from the issue detail panel in any view.
* **Bulk Assignment Manager** -- assign Strategic Parents to multiple Epics at once with filters, search, and batch operations.
* **CSV Export for Bulk Assignments** -- export the current Strategic Parent assignment table to CSV for offline review and sharing.

### Improvements

* **Payload fingerprinting** -- Hiera now fingerprints API payloads to avoid redundant re-renders when data has not changed, improving responsiveness on large projects.
* **Legacy storage migration** -- automatic migration of older Forge Storage formats to the current schema, ensuring backward compatibility after updates.
* **API error fallback** -- graceful fallback behavior when Jira API calls fail due to rate limits or transient errors, with retry logic and user notification.

### Bug Fixes

* **License check** -- resolved an issue where the license validation could fail intermittently on first load.
* **Pagination cap** -- fixed a bug where projects with more than 5,000 issues could hit an internal pagination limit, resulting in missing data.
* **Date parsing** -- corrected date parsing for locales that use non-ISO date formats, ensuring consistent behavior across Jira instances.
* **Parent badge** -- fixed a display issue where the parent badge on child items could show stale data after hierarchy changes.


---

# 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/release-notes.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.