Use GitHub forms for issues #15182
Use GitHub forms for issues #15182
Conversation
| Please feel free to add more information here to tell us about what you have tried. | ||
|
|
||
| - type: input | ||
| id: restart |
There was a problem hiding this comment.
Could this become a checkbox?
There was a problem hiding this comment.
It seems that the checkbox UX is more designed for what we do with pull requests, a list of checkboxes to confirm with.
I think using input allows people to add additional notes if relevant as well.
| description: | | ||
| Restarting your computer will help to ensure that software is in a fresh state. | ||
|
|
||
| - type: input |
There was a problem hiding this comment.
Could this be a checkbox?
| You can restart NVDA with add-ons disabled through the exit dialog. | ||
| In case the issue is caused by an add-on, it is recommended to contact the author of the add-on first. | ||
|
|
||
| - type: input |
There was a problem hiding this comment.
Could this be a checkbox?
GitHub is yet to support forms for pull requests: https://github.com/orgs/community/discussions/31664 |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
i really like this new form |
|
Due to accessibility issues with the form, this is blocked by https://github.com/orgs/community/discussions/61696 |
|
A GitHub bug has caused this to be closed an unable to be re-opened. #15320 has been opened instead |
Link to issue number:
None
Summary of the issue:
GitHub issue forms provide an easier and more clear way for users to report issues on the NVDA project.
Currently, when filling out an issue form, inline comments and an external guide is required to understand how to fill out an issue.
Description of user facing changes
When reporting an issue to NVDA, users can use the simpler GitHub forms interface.
Information from inline comments and the issue guide have been merged into this form, so that it is easier to understand the requirements.
Additionally, a new "custom issue" has been created, as we disable opening blank issues.
This should be used in the rare circumstance when the bug report or feature request template is not appropriate
Description of development approach
N/A
Testing strategy:
These changes have been pushed to a test repository
The new issue interface can be tested here: https://github.com/nvaccess/nvda-test/issues/new/choose
Example issues filled out using the form are as follows:
Known issues with pull request:
The current information for the bug report may be overly verbose.
However, it is rare that an issue reporter reads our external guide for reporting issues, and as such, inline information is preferred.
Change log entries:
N/A
Code Review Checklist: