forked from asonix/mastodon
Logically, it makes more sense to provide the steps leading up to the bug before asking what the bug is. This change moves "steps to reproduce" above "expected behavior" and "actual behavior" to enforce the above progression and logical flow.
42 lines
1.1 KiB
YAML
42 lines
1.1 KiB
YAML
name: Bug Report
|
|
description: If something isn't working as expected
|
|
labels: bug
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Make sure that you are submitting a new bug that was not previously reported or already fixed.
|
|
|
|
Please use a concise and distinct title for the issue.
|
|
- type: textarea
|
|
attributes:
|
|
label: Steps to reproduce the problem
|
|
description: What were you trying to do?
|
|
value: |
|
|
1.
|
|
2.
|
|
3.
|
|
...
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
attributes:
|
|
label: Expected behaviour
|
|
description: What should have happened?
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
attributes:
|
|
label: Actual behaviour
|
|
description: What happened?
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Specifications
|
|
description: |
|
|
What version or commit hash of Mastodon did you find this bug in?
|
|
|
|
If a front-end issue, what browser and operating systems were you using?
|
|
validations:
|
|
required: true
|