Bug Reporting – Notis

Quick start: say this

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.

Notis creates comprehensive bug reports from your screenshots and descriptions.

Bug reporting workflow

1. Capture the bug

Send a screenshot and describe what's wrong:

The 'Create Automation' button is duplicated and overlapping the sidebar.

Notis analyzes the screenshot and identifies the visual issue.

2. Provide reproduction steps

Notis asks clarifying questions:

Which browser and device?

What steps lead to this screen?

Does it happen every time?

Answer by voice or text:

I'm using Chrome on Mac. Go to the login page, then the Automations page, resize the window to half width, and the button duplicates. It happens every time.

3. Bug created in Linear + Notion

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

4. Assign and prioritize

Update the bug without leaving your chat:

Assign BUG-142 to Camille.

Mark it as High priority.

Add label: UI, Responsive.

Notis updates both Linear and Notion simultaneously.

Set up your Bugs tracker

Connect your bug tracker in the Integrations tab, or use the bug tracker included in the Notis Second Brain template.

⚠️

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.

💡

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 Notion 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.

Recommended Integrations

Integration	What it enables	Examples
Bug Tracker	Bug tracking, sprint management	Linear, Jira, GitHub Issues
Communication	Notify team of new bugs	Slack, Discord, Gmail

Automations

Comment received → keep the issue clean

When a comment is added to an issue in Linear, Notis extracts the actionable information and keeps the issue up to date.

Trigger: Comment Received Trigger

Go to the Automations tab in the Notis portal and create a new automation.

Select Linear and set the trigger to Comment Received Trigger.

Paste the instruction below (feel free to customize):

A comment was received on a Linear issue.

Goal: extract any new actionable info and keep the issue updated.

1) Summarize the comment in 1–3 bullets.

2) If the comment includes:
- new repro steps → propose a clean repro section
- environment details → capture them
- urgency/customer impact → propose priority/label updates (Customer, Escalation, Regression)

3) Update the Linear issue with:
- A concise comment summary (or add to description if appropriate)
- Any new labels if clearly justified

Output:
### Comment summary
- ...

### Proposed issue updates
- ...

Pro tips

Screenshot first: Visual context helps Notis understand the issue faster.

Be specific: "Button duplicated" is better than "something's wrong".

Mention frequency: "Every time" vs "sometimes" affects priority.

Include environment: Browser, OS, and device matter for debugging.