Bug Reporting

​

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.

​

Bug reporting workflow

​

1. Capture the bug

The ‘Create Automation’ button is duplicated and overlapping the sidebar.

​

2. Provide reproduction steps

• Which browser and device?
• What steps lead to this screen?
• Does it happen every time?

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

• BUG-142 – “Create Automation button duplicated on dashboard at small widths”
• Status: Triaged
• Full steps to reproduce
• Screenshot attached

• Mirrored entry with same details
• Linked to Linear issue
• Screenshot preserved

​

4. Assign and prioritize

Assign BUG-142 to Camille.

Mark it as High priority.

Add label: UI, Responsive.

​

Set up your Bugs tracker

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

​

Automations

​

Comment received → keep the issue clean

1. Go to the Automations tab in the Notis portal and create a new automation.
2. Select Linear and set the trigger to Comment Received Trigger.
3. 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.