Make installation method and API method mandatory in bug issue template #2342
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make installation method and API method mandatory in bug issue template
Pull Request Type
Please select what type of pull request this is:
Description
In the past people neglected to mention in an API related issue, what API they were using or installation method they were using in a installation they used that broke FT.
This was because the fields were not mandatory.
Additional context
I need some help on deciding what to do with the position of the API field. I would like to see all the mandatory fields first but i dont know what position sounds logical to move the API field to. Also im feeling a bit conflicted about changing the position because of the already logical order of all the fields.