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

# In-App Bug Button

> Report bugs from anywhere in HoLaCe — what it captures and how it ties to GitHub Issues.

HoLaCe ships with a one-click bug-report button that's available from every page. Click it, describe what happened, optionally attach a screenshot, and submit — your report goes directly to the HoLaCe engineering team's queue.

\[Screenshot: Bug report modal showing the description field, category dropdown, and screenshot upload area]

## Where the button lives

* **Sidebar footer** — a permanent **Report a Bug** button near the bottom of the sidebar.
* **Top bar** — a small bug icon in the top-right header.

Both open the same modal. Use whichever is closer to your cursor.

## What gets captured

When you submit, HoLaCe records:

| Field                 | Source                                                                    |
| --------------------- | ------------------------------------------------------------------------- |
| **Description**       | Your free-text input — be specific                                        |
| **Category**          | UI/UX, Functionality, Performance, Data, Auth, API, Database, Integration |
| **URL**               | Auto-filled from the page you were on                                     |
| **Error code**        | Optional paste field for any error you saw                                |
| **Screenshot**        | Optional upload (recommended)                                             |
| **Reporter**          | Your name and email                                                       |
| **Browser & OS**      | Auto-detected                                                             |
| **Screen resolution** | Auto-detected                                                             |

Auto-captured environment info means the engineering team doesn't have to ping you back asking "what browser were you using?" — that detail is already attached.

## How to write a good bug report

Three things make a bug actionable:

1. **What you did.** "I clicked Save on the demand letter editor."
2. **What you expected.** "I expected the letter to save and the modal to close."
3. **What happened.** "The modal froze and the page errored after 30 seconds."

A 30-second screenshot of the failed state is worth more than five minutes of typing. Use the screenshot upload.

## What happens after you submit

1. A `Bug` record is created in your firm's database (visible to firm admins on the **Bugs** page).
2. A matching **GitHub Issue** is filed in the HoLaCe engineering repo, including all environment metadata and your screenshot.
3. The bug shows up in the engineering team's triage queue within seconds.
4. As the bug moves through fixed → released, your `Bug` record updates — open / in progress / resolved / closed — and you'll see it on the Bugs page.

For beta-testing firms, the team typically responds same day. For everyone else, expect triage within 24 business hours.

## Tracking your reports

**Sidebar → Bugs** (visible to firm admins) shows every bug your firm has reported, with status, category, and resolution. Click any row for the full thread including developer notes when the team writes back.

If a bug you reported is fixed and shipped, you'll see the resolution comment on the Bugs page and the linked GitHub issue close automatically.

## What this isn't

The bug button is for **product issues** — something is broken, wrong, or confusing. It is not the right channel for:

* **Feature requests** — use the Feature Requests page in the admin portal.
* **Account / billing questions** — email HoLaCe support directly.
* **Time-sensitive emergencies** ("I can't sign in for a deposition in 30 minutes") — call your designated HoLaCe support contact.

<Note>
  See also: [Support Tickets](/admin-cross-cutting/support/support-tickets) for the broader support workflow (currently dormant).
</Note>