Add two additional fields to the Problem report template in GitHub:
"Package(s) name" – can be a multiselect field with the packages managed in this repository (@adyen/lume, @adyen/lume-vue3, etc.)
"Package(s) version" – can be a multiselect field with all published versions, or just an input field so users would be able to use semver range.
Problem/motivation
When I make a new Problem report to this repository in GitHub, there is already predefined template with required and optional information that has to be filled in. This is very helpful as it allows to collect as much context about the issue as possible, like "Browser" or "OS".
However I think it would be helpful to add two more fields described above as it may be a crucial information to have. For example, some of the issues reported to older version may have been fixed already. So knowing the version can easily highlight if that is "already fixed issue" or it is a "regression issue".
Describe alternatives you've considered
This information can be provided as a free-form input, but it is not asked anywhere. So there is a high chance it will not be provided.
Feature description
Add two additional fields to the Problem report template in GitHub:
@adyen/lume,@adyen/lume-vue3, etc.)Problem/motivation
When I make a new Problem report to this repository in GitHub, there is already predefined template with required and optional information that has to be filled in. This is very helpful as it allows to collect as much context about the issue as possible, like "Browser" or "OS".
However I think it would be helpful to add two more fields described above as it may be a crucial information to have. For example, some of the issues reported to older version may have been fixed already. So knowing the version can easily highlight if that is "already fixed issue" or it is a "regression issue".
Describe alternatives you've considered
This information can be provided as a free-form input, but it is not asked anywhere. So there is a high chance it will not be provided.
Additional context
No response
Validations