# OKR View The OKR View organizes your issues into a tree grouped by objectives, providing automatic completion rollup and health indicators. It connects day-to-day work items to strategic goals. ## How It Works The OKR View uses your configured hierarchy to build a tree where top-level items represent objectives and their children represent key results or contributing work. Completion and health metrics roll up from leaf-level items to their parent objectives. ## Completion Rollup Completion percentage is calculated from the bottom up: * **Leaf-level items** (e.g., Stories, Tasks) contribute their individual status (done or not done) * **Parent items** (e.g., Epics, Initiatives) aggregate completion from their children * The resulting percentage is displayed as a progress bar on each node in the tree This means you do not need to manually update objective progress -- it is derived automatically from the status of contributing work. ## Health Indicators Each item in the tree receives a health status based on two factors: * **Date compliance** -- whether the item is on schedule relative to its Start Date and End Date * **Blocker status** -- whether the item or any of its children are blocked by dependencies Health is displayed as a color-coded indicator: * **On track** -- dates are within range and no blockers exist * **At risk** -- approaching end date or minor blockers detected * **Off track** -- past due or blocked by unresolved dependencies ## Tree Navigation Expand or collapse any node in the tree to drill into specific objectives or roll up to a strategic summary. The tree respects toolbar filters, so you can focus on a specific team, area, or quarter. ## Practical Tips * Use the OKR View during quarterly reviews to assess objective health at a glance. * Combine with the Timeline view to investigate specific items that are off track. * Ensure all contributing issues have dates set for accurate health calculations. --- # 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/okr-view.md?ask= ``` 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.