tab-stash/.github/ISSUE_TEMPLATE/1-crash-report.yml

83 lines
3.4 KiB
YAML

name: Report a Crash
description: Tab Stash notified you about a crash, and you have the crash details.
labels: ["i-bug"]
body:
- type: markdown
attributes:
value: |
Sorry to hear you're having trouble, and thanks for taking the time to report a crash!
If you're not sure whether you have one problem or multiple problems, it's better to err on the side of opening separate reports for each potential problem, since it's much easier to close duplicates than split a single issue into multiple issues.
- type: textarea
id: crash-details
attributes:
label: Crash Details
render: text
description: |
Paste crash details from Tab Stash here. (If you don't have crash details, please use the "Report a Bug" option instead.)
placeholder: |
Browser: Mozilla Firefox ...
Extension: Tab Stash ...
validations:
required: true
- type: textarea
id: installed-extensions
attributes:
label: Installed Extensions
description: |
List all other extensions you have installed. Also, please double-check to make sure you don't have any extensions installed which are [incompatible with Tab Stash](https://github.com/josh-berry/tab-stash/wiki/Known-Incompatibilities-with-Other-Extensions).
value: "- "
validations:
required: true
- type: textarea
id: actual-behavior
attributes:
label: Describe the Crash
description: |
Describe what you were doing before the crash in as much detail as possible. If you can, list any steps you followed which may have led to the crash.
placeholder: |
1. I clicked the widget
2. The "Edit Widget" dialog appeared
3. I clicked on "Encabulate"
4. The crash happened
validations:
required: true
- type: textarea
id: expected-behavior
attributes:
label: Expected Behavior
description: |
Describe what you expected to happen instead.
- type: textarea
id: impact
attributes:
label: Impact
description: |
If you tried anything to work around or recover from the bug, or if the bug caused additional problems, discuss it here. Be as concrete, specific and detailed as possible.
For example, "I spent an hour trying to restart the encabulator to retrieve my data after the crash" clearly illustrates the scale and scope of the problem. Whereas, "This is a huge problem and should be fixed ASAP" is likely to be ignored because it doesn't provide any detail about WHY the problem is huge.
- type: textarea
id: details
attributes:
label: Additional Details
description: |
Any other context that might be helpful.
- type: checkboxes
id: voting
attributes:
label: Vote for This Issue
description: Please check the box below so GitHub will tell everyone how to vote for your issue—sorry, I know it's an unnecessary step, but that's the only way GitHub will allow me to include this message in the issue itself.
options:
- label: |
_Readers: If you are also experiencing this problem, please vote for it by giving the ORIGINAL POST a thumbs-up using the :smiley: button below. You are welcome to leave comments and discuss the issue if you have more details to add, but "Me too!" comments are not counted by the voting system._
required: true
validations:
required: true