> ## Documentation Index
> Fetch the complete documentation index at: https://docs.typewise.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Bug reports

> Report platform issues through the AI Operator and review them in the Bug reports dashboard

When something in the Typewise Platform looks broken, you can report it directly
through the [AI Operator (Nova)](/documentation/nova/getting-started). Reports
go straight to the Typewise team, and admins can review every report submitted
by their company in the [Bug reports
dashboard](#bug-reports-dashboard-admins).

This replaces the legacy "Send Feedback" widget for users who have the AI
Operator enabled.

***

## Reporting a bug through the AI Operator

<Steps>
  <Step title="Open the AI Operator">
    Open the AI Operator panel from anywhere in the Platform.
  </Step>

  <Step title="Describe what went wrong">
    Tell the Operator what happened in your own words, for example, "I found a
    bug: the CSAT chart is blank when I apply a specialist filter." The Operator
    picks up on phrases like "I found a bug", "this is broken", or "report
    this".
  </Step>

  <Step title="Answer any clarifying questions">
    The Operator may ask one or two short follow-ups to fill in the gaps (for
    example, what page you were on, or whether the screen showed an error or
    just stayed blank).
  </Step>

  <Step title="Choose whether to attach the current ticket">
    If you're on a ticket page when you report the issue, the Operator will ask
    whether to attach that ticket to the report. Attach it when the bug is about
    that specific ticket; skip it for general issues like layout or navigation
    problems.
  </Step>

  <Step title="Review and confirm the draft">
    The Operator will show you a short title and a clean description of the
    issue. Reply with **yes** (or "send it", "go", etc.) to submit, or ask for
    changes if anything looks wrong.
  </Step>

  <Step title="Get confirmation">
    Once submitted, the Operator confirms that your report was received. The
    Typewise team will follow up if they need more information.
  </Step>
</Steps>

<Tip>
  A good bug report answers three questions: **What happened?** (what you
  actually saw), **What did you expect?** (what should have happened instead),
  and **How can it be reproduced?** (which page, which action, which filter,
  which entity). The more of these you include up front, the fewer follow-ups
  the Operator needs to ask.
</Tip>

***

## Checking the status of past reports

Admins can also ask the AI Operator to recap reports already submitted by their
company.

Try phrases like:

* "What bugs have I reported?"
* "Status of the bug I reported yesterday"
* "Any open issues from my team?"

The Operator will list recent reports submitted by your company, with a short
title, current status, and how long ago each one was submitted. If the list is
long, you can ask for older entries.

<Info>
  Reports are scoped to your company, so you'll see issues submitted by any user
  at your organization, not just your own.
</Info>

<Note>
  Listing past reports through the AI Operator is available to admin users only.
  Non-admin users can still submit new reports. They just won't be able to see
  the full history. For a full overview, admins can open the [Bug reports
  dashboard](#bug-reports-dashboard-admins).
</Note>

***

## What's not supported today

<Note>
  Feature requests aren't supported through the AI Operator yet, only bug
  reports. If you'd like to suggest an improvement, share it through your usual
  Typewise contact. Adding attachments to a report directly through the Operator
  is also not yet available.
</Note>

***

## Bug reports dashboard (admins)

Admins can review every report submitted by their company in the **Bug reports
dashboard**.

### Opening the dashboard

Click your avatar in the bottom-left of the sidebar to open the user menu, then
select **Bug reports**. The entry only appears for admin users.

### What you'll see

The dashboard shows a paginated table of every bug report submitted by users at
your company.

| Column            | Description                                                                            |
| :---------------- | :------------------------------------------------------------------------------------- |
| **Title**         | The short summary the AI Operator drafted when the report was submitted.               |
| **Report ID**     | The identifier the Typewise team uses to track the report internally.                  |
| **Description**   | The full description of the issue, with reproduction steps and context.                |
| **Created by**    | The email of the user who submitted the report.                                        |
| **Creation date** | When the report was submitted.                                                         |
| **Status**        | The current state of the report (see [Statuses](#statuses)).                           |
| **Ticket ID**     | The Typewise ticket the report is linked to, if the user attached one when submitting. |

### Statuses

Every report falls into one of three statuses:

| Status          | Meaning                                                                                   |
| :-------------- | :---------------------------------------------------------------------------------------- |
| **Open**        | The report has been received but the Typewise team hasn't started working on it yet.      |
| **In Progress** | The Typewise team is actively investigating or fixing the issue.                          |
| **Done**        | The issue has been resolved, or the report has been closed (for example, as a duplicate). |

### Filtering and search

* **Search**: Use the search bar above the table to filter reports by any field, title, description, reporter, ticket ID, and so on.
* **Status filter**: Click the filter icon next to the search bar to show only
  **Open**, **In Progress**, or **Done** reports. Choose **All statuses** to
  clear the filter.
* **Pagination**: Navigate between pages and adjust the page size from the
  controls at the bottom of the table.

### Report details

Click any row to open a side panel with the full report:

* The complete description, with formatting and any images the user attached.
* Who submitted the report and when.
* The linked Typewise ticket ID, if one was attached.

<Tip>
  Use the dashboard to keep your team in the loop on what's been reported, spot
  patterns across multiple reports, and confirm whether an issue you've noticed
  has already been raised.
</Tip>

***

## See also

* [Simulator](/documentation/testing-and-feedback/simulator): Test AI
  conversations before publishing changes
* [Automated Tests](/documentation/testing-and-feedback/tests): Validate AI
  Agent behavior with repeatable test scenarios
* [AI feedback](/documentation/tickets/ai-feedback): Flag incorrect AI replies
  or actions on a specific ticket (different from reporting a Platform bug)