> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/management/reporting-a-ui-issue.md).

# Reporting a UI Issue

Some UI issues are easy to reproduce and describe. Others are intermittent, browser-specific, or only show up under certain data conditions — a report rendering incorrectly, a count that flickers, a page that partially loads. For those harder-to-pin-down cases, a **HAR file** is the fastest way to get support the information they need to diagnose it.

{% hint style="info" %}
A HAR (HTTP Archive) file captures the network requests your browser made while the issue occurred — it lets support see exactly what the app requested and what came back, without you needing to reproduce the issue live on a call.
{% endhint %}

## When to create a HAR file

Reach for a HAR file when the issue is:

* Intermittent or hard to reproduce reliably.
* Specific to certain data, tenants, or timing.
* Something you can trigger, but can't easily explain in words (a display glitch, incorrect counts, a page that hangs).

## How to create a HAR file

1. Open your web browser (Chrome, Edge, Firefox, etc.) and go to the page where the issue occurs.
2. Open Developer Tools — press **F12**, or right-click the page and select **Inspect** (or **Inspect Element**).
3. In Developer Tools, select the **Network** tab.
4. Reload the page, or perform the action that triggers the issue, while the Network tab is open and recording.
5. Once the network requests have been captured, right-click anywhere in the Network tab and select **Save all as HAR**.
6. Choose a location to save the file and give it a descriptive name (for example, `mfa-report-count-bug.har`).
7. Attach the saved `.har` file to your support ticket.

{% hint style="warning" %}
The exact steps can vary slightly by browser and version, but the overall process — open Developer Tools, go to Network, reproduce the issue, save as HAR — is consistent across Chrome, Edge, and Firefox. Some browsers may require you to enable network logging/capture before recording will work.
{% endhint %}

## What to include with your ticket

A HAR file is most useful when paired with a bit of context. When you file the ticket, also include:

* The exact page/URL and the tenant or company you were viewing.
* What you expected to see vs. what actually happened.
* A screenshot, if the issue is visual (for example, a display showing incorrect user counts, or a display glitch specific to one browser).
* Whether the issue is consistent or intermittent.

{% hint style="info" %}
Real examples we've seen come in this way include a read-only user seeing intermittent, inconsistent counts on an MFA view, and browser-specific rendering differences (for example, a display issue that only appeared in one browser's dark mode). Details like the browser, whether dark mode or any custom branding was enabled, and how often it recurs all help narrow down the cause faster.
{% endhint %}


---

# 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://helpdesk.augmentt.com/management/reporting-a-ui-issue.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.