The issue template is currently designed to streamline bug reports. However, per CONTRIBUTING.md, issues can also be used for feature requests...
For large features or changes, please open an issue and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
Here's an example of an ISSUE_TEMPLATE from another project I've contributed to that accounts for both bug reports, and feature requests.
I have an idea for a feature request
I click the "New Issue" button on the "Issues" tab
There is a template explaining the standard format for feature requests
The template only shows the format for bug reports
Here's another one that's a bit more brief but covers both bugs and features: https://www.talater.com/open-source-templates/#/page/98
Nice idea, except when you actually do post a feature request in here, it might instantly get a response referencing https://community.magento.com/t5/News-Announcements/Improvements-to-GitHub-Management/m-p/44572#M96
And after an issue gets the "improvement" label, then there's a bot handling the issue in the following manner: http://take.ms/KDbuS
Alright, that puts this idea to rest then :P
I see. It might be worth updating the issue template to state that process, then. Also contributing.md says to open an issue, so that should be corrected as well.
If you would like submit a feature request, please, create it here: https://github.com/magento-engcom/community-features/issues/
If you would like submit a feature request, please, create it here: https://github.com/magento-engcom/community-features/issues/
Wow, that's new. Does that mean the feature requests posted to Community Forums will be disregarded from now on (unless they have corresponding issues at engcom repo) or will you process those separately somehow?
If https://github.com/magento-engcom/community-features/issues/ is officially the new "go-to place" for feature requests, wold you mind to kindly update the Readme.MD file for this repository and/or announce this information via other channels (devblog, email newsletter, etc.) ?
Most helpful comment
I see. It might be worth updating the issue template to state that process, then. Also contributing.md says to open an issue, so that should be corrected as well.