ci: question.yml - Clarify that the issue tracker is not for personal support (#3498)

* ci: Revise `question.yml` to better clarify the issue tracker is not for support queries

Users have been making low effort reports (_bypassing the dedicated form_) through this alternative that is intended for addressing other concerns related to the project - not troubleshooting user problems.

When a user does not want to put the effort in of a full bug report (_and following our debug docs tips that it refers them to_), they should be using the Github Discussions page which provides the same free-form input, but should not require attention of project devs (contributors / maintainers).

---

The markdown rendered field above the "Description" input field didn't seem too relevant for this template. I've opted for a markdown comment (so it won't render if kept) into the input field with hopes that'll be more visible to the readers attention.

* chore: Fix typo
This commit is contained in:
Brennan Kinney 2023-08-24 02:56:24 +12:00 committed by GitHub
parent 39ae101266
commit af09db6648
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1,18 +1,10 @@
name: Other name: Other
description: Miscellaneous questions and reports description: Miscellaneous questions and reports for the project (not support)
title: 'other: ' title: 'other: '
labels: labels:
- meta/help wanted - meta/help wanted
body: body:
- type: markdown
attributes:
value: |
Markdown formatting can be used in almost all text fields. The description will tell you if this is not the case for a specific field.
Be as precise as possible, and if in doubt, it's best to add more information that too few.
---
- type: dropdown - type: dropdown
id: subject id: subject
attributes: attributes:
@ -21,8 +13,7 @@ body:
- I would like to contribute to the project - I would like to contribute to the project
- I would like to configure a not documented mail server use case - I would like to configure a not documented mail server use case
- I would like some feedback concerning a use case - I would like some feedback concerning a use case
- I have questions about TLS/SSL/STARTTLS/OpenSSL - Something else that requires developers attention
- Other
validations: validations:
required: true required: true
- type: textarea - type: textarea
@ -31,3 +22,9 @@ body:
label: Description label: Description
validations: validations:
required: true required: true
value: |
<!---
Please do not use this form to bypass doing a proper bug report.
The issue tracker is for anything relevant to the project itself, not individual support queries.
If you don't want to fill out a bug report, please ask support questions at our community discussions page: https://github.com/orgs/docker-mailserver/discussions
-->