> For the complete documentation index, see [llms.txt](https://docs.duku.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duku.ai/viewport-dashboard/issues.md).

# Issues

The Issues page shows the problems Duku has found on your app.

<figure><img src="/files/lWPq5c4rOWrNSyttfaMV" alt="Teddy issues page"><figcaption></figcaption></figure>

Each row is one distinct issue. Repeat occurrences stay grouped together, so you see counts, **first seen**, and **last seen** instead of duplicate noise.

### <i class="fa-triangle-exclamation">:triangle-exclamation:</i> What you can do

* Filter by **Open**, **Triaged**, **Resolved**, or **Ignored**
* Search by issue name
* Narrow to issues blocking your tests
* Sort by priority or recency
* Update status or priority for multiple issues at once

### <i class="fa-table-list">:table-list:</i> Issue list

The issue list helps you review what matters first.

Each row shows the issue name, status, priority, occurrence count, and when it was first and last seen.

Use the list to focus on fresh regressions, long-running problems, or issues affecting test coverage.

### <i class="fa-magnifying-glass">:magnifying-glass:</i> Issue detail

Open an issue to inspect it in detail.

You can review:

* The issue title and priority
* A 14-day chart showing how often it has occurred
* A sample failure with where it happened and the relevant detail
* A side panel with status, priority, category, first seen, last seen, occurrence count, and affected builds

### <i class="fa-timeline">:timeline:</i> Timeline

Below the summary, the timeline shows every occurrence for that issue.

Open any timeline entry to jump to the exact run where the problem happened.


---

# 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://docs.duku.ai/viewport-dashboard/issues.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.
