Skip to content

Commit

Permalink
update bug_report template
Browse files Browse the repository at this point in the history
  • Loading branch information
mynameisbogdan committed Apr 1, 2024
1 parent a5364b1 commit d8273ca
Showing 1 changed file with 12 additions and 5 deletions.
17 changes: 12 additions & 5 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
Expand Up @@ -38,12 +38,12 @@ body:
description: |
examples:
- **OS**: Ubuntu 20.04
- **Prowlarr**: Prowlarr 0.1.0.650
- **Prowlarr**: Prowlarr 1.15.0.4361
- **Docker Install**: Yes
- **Using Reverse Proxy**: No
- **Browser**: Firefox 90 (If UI related)
value: |
- OS:
- OS:
- Prowlarr:
- Docker Install:
- Using Reverse Proxy:
Expand All @@ -63,11 +63,18 @@ body:
required: true
- type: textarea
attributes:
label: Trace Logs?
label: Trace Logs? **Not Optional**
description: |
Trace Logs (https://wiki.servarr.com/prowlarr/troubleshooting#logging-and-log-files)
***Generally speaking, all bug reports must have trace logs provided.***
Trace Logs (https://wiki.servarr.com/prowlarr/troubleshooting#logging-and-log-files)
***Generally speaking, all bug reports MUST have trace logs provided.***
Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
Additionally, any additional info? Screenshots? References? Anything that will give us more context about the issue you are encountering!
validations:
required: true
- type: checkboxes
attributes:
label: Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.
description: Trace logs are **generally required** and are not optional for all bug reports and contain `trace`. Info logs are invalid for bug reports and do not contain `debug` nor `trace`
options:
- label: I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.
required: true

0 comments on commit d8273ca

Please sign in to comment.