GitHub issue template for bug reports (YAML form + Markdown)

name: Bug report
description: Something does not work as expected.
title: 'Bug: [Area]: [what goes wrong] when [trigger]'
labels:
- bug
- needs-triage
body:
- type: markdown
  attributes:
    value: |
      The default for anything that works incorrectly. If it fits a more specific template below, use that instead.
- type: input
  id: summary
  attributes:
    label: Summary
    description: 'One sentence: what breaks and who it affects.'
  validations:
    required: true
- type: textarea
  id: environment
  attributes:
    label: Environment
    description: Version or build, URL or screen, browser or device + OS, account/plan, feature flags.
    value: "Build: \nURL / screen: \nBrowser or device + OS: \nAccount / plan: \nFlags: \n"
  validations:
    required: true
- type: textarea
  id: steps
  attributes:
    label: Steps to reproduce
    description: Start from a known state. One action per step.
    value: "1. Logged in as \n2. \n3. \n"
  validations:
    required: true
- type: textarea
  id: expected
  attributes:
    label: Expected result
    description: What should happen. Link the spec or last working version if you can.
  validations:
    required: true
- type: textarea
  id: actual
  attributes:
    label: Actual result
    description: What happens instead. Paste the exact error text.
  validations:
    required: true
- type: dropdown
  id: frequency
  attributes:
    label: How often does it happen?
    options:
    - Always (every try)
    - Often (more than half of tries)
    - Sometimes (less than half)
    - Once so far
  validations:
    required: true
- type: dropdown
  id: severity
  attributes:
    label: Severity (see the severity guide)
    description: Triage may change it.
    options:
    - '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)
  validations:
    required: true
- type: textarea
  id: evidence
  attributes:
    label: Evidence
    description: Drag in a screen recording or screenshot. Add console errors, request IDs or log links.
  validations:
    required: false
- type: textarea
  id: logs
  attributes:
    label: Console or log output
    description: Paste text, not screenshots of text. Remove secrets and personal data.
    render: shell
  validations:
    required: false
- type: input
  id: workaround
  attributes:
    label: Workaround
    description: What users can do meanwhile, or "none known".
  validations:
    required: false
- type: checkboxes
  id: checks
  attributes:
    label: Before you submit
    options:
    - label: I searched existing issues and this is not a duplicate
      required: true
    - label: I removed passwords, tokens and personal data from attachments
      required: true

blank_issues_enabled: false
contact_links:
- name: Report a security vulnerability (private)
  url: https://github.com/OWNER/REPO/security/advisories/new
  about: Please do not open a public issue for security problems.
- name: Customer support
  url: https://example.com/support
  about: Account or billing questions go to support. Replace this link.

---
name: Bug report
about: Something does not work as expected.
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. -->
```shell

```

### 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 attachments