Convert Issue Template to YAML #6507
Conversation
|
if we want to validate on the Jellyfin versioning in the template, this will inherently require more maintenance. Each release, this would require an update as well. One option is to tie it into our release system to be updated to take care of the need to update it manually. |
| - type: dropdown | ||
| id: version | ||
| attributes: | ||
| label: Jellyfin Version | ||
| description: What version of Jellyfin are you running? | ||
| options: | ||
| - 10.7.7 | ||
| - 10.7.z | ||
| - 10.6.4 | ||
| - Other | ||
| validations: | ||
| required: true |
There was a problem hiding this comment.
Jellyfin versioning validation
| name: Issue Report | ||
| description: File an issue report | ||
| title: "[Issue]: " |
There was a problem hiding this comment.
Why the name change from "Bug Report" to "Issue Report"?
There was a problem hiding this comment.
Lots of people report issues, not necessarily bugs. If it is a bug, then we can confirm it and keep the stale bot away.
There was a problem hiding this comment.
So should the [bug] label (on line 4) be changed to an [issue] label? I'm too new to the project to have a good feel for how the labels are being used.
There was a problem hiding this comment.
we'd have to make an issue label for that to work. Might be best to just remove it and leave triage only
Old
https://github.com/jellyfin/jellyfin/issues/new?assignees=&labels=bug&template=bug_report.md&title=
New
https://github.com/Artiume/jellyfin/issues/new?assignees=&labels=bug%2Ctriage&template=Bug+Report.yml&title=%5BIssue%5D%3A+