0aa76567a6
When an issue has been already handled by our part, and thus gets closed, but affects many users and the fix takes a while to be rolled out, it usually happens that those who notice the matter later on don't notice previous reports and create duplicate issues. Let's try to improve a little bit on that by not filtering out closed issues in the links for checking whether the same issue was already reported before. This should make it more obvious to users who follow the link whether an issue for their problem already exists.
42 lines
1.3 KiB
YAML
42 lines
1.3 KiB
YAML
name: 🛠️ API issue (api.modrinth.com)
|
|
description: Report an issue regarding the Modrinth API.
|
|
labels: [bug, backend]
|
|
body:
|
|
- type: checkboxes
|
|
attributes:
|
|
label: Please confirm the following.
|
|
options:
|
|
- label: I checked the [existing issues](https://github.com/modrinth/code/issues?q=is%3Aissue) for duplicate problems
|
|
required: true
|
|
- label: I have tried resolving the issue using the [support portal](https://support.modrinth.com)
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Describe the bug
|
|
description: A clear and concise description of what the bug is. Include screenshots if applicable.
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
attributes:
|
|
label: Steps to reproduce
|
|
description: Steps to reproduce the behavior.
|
|
placeholder: |
|
|
1. Go to '...'
|
|
2. Click on '...'
|
|
3. Scroll down to '...'
|
|
4. See error
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
attributes:
|
|
label: Expected behavior
|
|
description: A clear and concise description of what you expected to happen.
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
attributes:
|
|
label: Additional context
|
|
description: Add any other context about the problem here.
|
|
validations:
|
|
required: false
|