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

# Bug Reporting (via Notion)

> Track bugs in the Features and Bugs database from the Notis Second Brain template, mirror Linear issues into Notion, and enforce a bug report template with database instructions.

Use the Notion **Features and Bugs** database as your bug tracker, on its own or mirrored with Linear, so every report you dictate lands in Notion with the screenshot and reproduction steps attached.

## What this setup does

Notis reads and writes your Notion databases. With the Features and Bugs database from the Second Brain, Notis can:

* Create a bug entry from a screenshot and a voice note

* Mirror each Linear issue as a Notion entry linked to the issue

* Update both Linear and Notion when you assign, prioritize, or label a bug

* Collect every required detail before creating an entry, following the template you set in the database description

## Step 1: Set up your Bugs database

The [Notis Second Brain](/notion/second-brain) already contains a [bug tracker](/get-started/notion) set up for you.

<Warning>
  If you choose to use a bug tracker like Linear or Jira, make sure to delete the bug tracker database in the Notis Second Brain template to avoid any conflicts.
</Warning>

## Step 2: Enforce a bug report template

<Tip>
  If you want to enforce a template for reporting bugs or creating new user stories, you can modify the Features and Bugs database description to enforce a template and ask Notis to collect all relevant information before creating a new entry. Here’s an example:

  ```
  Bug Report Format
  Title: Short summary.
  Description: What’s the problem?
  Steps to Reproduce: Numbered steps.
  Expected Result: What should happen?
  Actual Result: What happened instead?
  Environment: (e.g., OS, version)
  Screenshots/Logs: (Optional)

  Feature Request Format
  Title: Short summary.
  Description: What’s the feature?
  Use Case: Why is it useful?
  Additional Details: (Optional)

  If any information is missing, ask the user before creating new entries, as we don't want vague bug reports or vague user stories. You are responsible for ensuring you get all the context (e.g., steps to reproduce) before creating a new entry.
  ```
</Tip>

See [database instructions](/notion/database-instructions) for how Notis reads the database description.

## Step 3: Ask Notis to use it

> *There's a UI bug on my dashboard. The Create button is duplicated.*

> *Log this as a bug in Linear and my Notion Bugs database.*

> *Assign BUG-142 to Camille and mark it as high priority.*

When you keep Linear and Notion in sync, Notis creates synchronized entries:

**In Linear:**

* **BUG-142** – "Create Automation button duplicated on dashboard at small widths"

* Status: Triaged

* Full steps to reproduce

* Screenshot attached

**In Notion Bugs database:**

* Mirrored entry with same details

* Linked to Linear issue

* Screenshot preserved

Later updates ("Assign BUG-142 to Camille", "Mark it as High priority", "Add label: UI, Responsive") are applied to both Linear and Notion simultaneously.