> 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

Review distinct problems found across your app.

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

Learn how Duku groups errors into issues in [Issues & signals](/core-concepts/issues-and-signals.md).

Read and triage issues programmatically with the [Issues API](/integrations/issues-api.md).

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2F8zhp3rsKdDIgAhrNNnkO%2Fduku-issues-2026-09-11.png?alt=media&amp;token=fbdce5e0-39d3-44a4-b61a-efce1ab2daa3" alt=""><figcaption></figcaption></figure>

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

* Filter by **All**, **Open**, **Triaged**, **Resolved**, or **Ignored**
* Sort by priority, runs, first seen or last seen
* Change status or priority from any row
* Search by title and update several issues at once
* Show only visual issues from the filter in the **Issue** column header

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

The issue list helps you review what matters first.

Each row shows the issue, its status and priority, how many signals and runs are behind it, and when it was first and last seen.

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

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

Open an issue to inspect it in detail.

The Details card includes a **Ticket** row. Select **Create ticket** to file the issue in Linear. See [Linear](/integrations/linear.md) for the ticket flow and stage sync.

<figure><img src="https://1135428273-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2rbi6bEnpVLUQHudgXDV%2Fuploads%2FP7lTu8cTX1fkoBoFwD0h%2Fduku-issue-detail-2026-09-11.png?alt=media&amp;token=38c861ca-49fc-473a-9c55-e60b86f35332" alt=""><figcaption></figcaption></figure>

You can review:

* The issue title and priority
* The signals behind it
* For a visual issue, the screenshot it was found on and what is wrong
* A 14-day chart showing how often it has occurred
* An **Analysis** card describing the problem, with **Copy**
* A Details card with status, priority, ticket, first seen, last seen, signals and affected runs

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

Below the summary, **Affected runs** lists every run that hit the issue.

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