BobbinQuick answer
In Linear, go to Team settings → Templates, create a template, paste the description below and preset the label (Bug) and status (Triage). If every report must include steps and severity, build a form template from the field plan instead: Linear's docs say any field in a form template can be required (checked 23 October 2026).
Description for a standard template
Linear descriptions take Markdown-style formatting when pasted. In template editing, Linear also offers placeholder formatting (the Aa option) for the italic hints.
**Template:** Bug report · **Title:** `Bug: [Area]: [what goes wrong] when [trigger]` · **Labels:** bug, needs-triage
### Summary (required)
_One sentence: what breaks and who it affects._
### Environment (required)
_Version or build, URL or screen, browser or device + OS, account/plan, feature flags._
Build:
URL / screen:
Browser or device + OS:
Account / plan:
Flags:
### Steps to reproduce (required)
_Start from a known state. One action per step._
1. Logged in as
2.
3.
### Expected result (required)
_What should happen. Link the spec or last working version if you can._
### Actual result (required)
_What happens instead. Paste the exact error text._
### How often does it happen? (required)
_Tick one._
- [ ] Always (every try)
- [ ] Often (more than half of tries)
- [ ] Sometimes (less than half)
- [ ] Once so far
### Severity (see the severity guide) (required)
_Triage may change it._
_Tick one._
- [ ] S1 Critical: data lost/exposed or core flow blocked, no workaround
- [ ] S2 Major: core feature wrong or failing for a group
- [ ] S3 Minor: works with an easy workaround
- [ ] S4 Cosmetic: looks or reads wrong only
- [ ] Not sure (triage will set it)
### Evidence
_Drag in a screen recording or screenshot. Add console errors, request IDs or log links._
### Console or log output
_Paste text, not screenshots of text. Remove secrets and personal data._
```
```
### Workaround
_What users can do meanwhile, or "none known"._
### Before you submit (required)
- [ ] I searched existing issues and this is not a duplicate
- [ ] I removed passwords, tokens and personal data from attachmentsField plan for a form template
Linear form templates support Text, Long text, Dropdown, Checkboxes, Date and Instructions fields, plus property fields such as title, priority and label group. Map T1 like this:
| Field | Linear field type | Required | Options or hint |
|---|---|---|---|
| Summary | Text | Yes | One sentence: what breaks and who it affects. |
| Environment | Long text | Yes | Version or build, URL or screen, browser or device + OS, account/plan, feature flags. |
| Steps to reproduce | Long text | Yes | Start from a known state. One action per step. |
| Expected result | Long text | Yes | What should happen. Link the spec or last working version if you can. |
| Actual result | Long text | Yes | What happens instead. Paste the exact error text. |
| How often does it happen? | Dropdown | Yes | Always (every try); Often (more than half of tries); Sometimes (less than half); Once so far |
| Severity (see the severity guide) | Dropdown | Yes | S1 Critical: data lost/exposed or core flow blocked, no workaround; S2 Major: core feature wrong or failing for a group; S3 Minor: works with an easy workaround; S4 Cosmetic: looks or reads wrong only; Not sure (triage will set it) |
| Evidence | Long text | No | Drag in a screen recording or screenshot. Add console errors, request IDs or log links. |
| Console or log output | Long text | No | Paste text, not screenshots of text. Remove secrets and personal data. |
| Workaround | Text | No | What users can do meanwhile, or "none known". |
| Before you submit | Checkboxes | Yes | I searched existing issues and this is not a duplicate; I removed passwords, tokens and personal data from attachments |
Use Linear's own Priority property for priority, and keep severity as the dropdown, so the two stay separate (why that matters).
Record the video part
Drag the MP4 into the Evidence part of the issue description. Bobbin is a free Chrome extension that records your screen, a window or a tab with your microphone and an optional webcam bubble. No account, no watermark, no time limit, and nothing is uploaded: the file stays on your computer.
- Click the Bobbin icon in Chrome's toolbar and choose Record screen, window or tab.
- Pick your microphone and turn on the camera if you want the webcam bubble.
- Press Start recording, choose what to share in Chrome's picker, and wait for the 3-second countdown.
- Pause with Alt+Shift+P, stop with Alt+Shift+S, then press Download to save the file.
To keep other tabs and notifications out of it, share just the Chrome tab (the webcam bubble appears only in screen and window recordings). Bobbin saves MP4 where your browser supports it (Chrome 126 or newer), WebM otherwise, and tells you which it used.
File size: our 60-minute 1080p test came to about 246 MB (roughly 4 MB a minute) on a simple synthetic screen; busy real screens can be larger, so a 1–2 minute clip is usually small enough to attach.
From The Bug Report & QA Kit
The kit has all 10 bug templates in Linear format, plus Jira, GitHub and Markdown versions. The full kit: 10 bug templates for GitHub, Jira, Linear and Markdown, 9 release checklists (126 checks), the severity guide, 8 bug-video scripts and trackers.
See the QA kit ($15, one-time) PDF + ZIP · 7-day refund · more free samples on the page
Checked on 23 October 2026 from their own pages: Linear Docs: Issue templates. Features change; check the linked page before you rely on it.
Loom, Vidyard, Tella, Tango, Screencastify, Screenity, Zoom and Slack are trademarks of their respective owners. Bobbin is not affiliated with them. Prices and plan limits from their public pages as of 22 Oct 2026.