☂️ Proposal to make improvements to existing new issue templates.

[darshankawar]

Based on the discussion happened on discord, we thought of proposing below ideas / improvements to the existing new issue template.

Use case

We as triagers come across a lot of issues that are either:

1. Empty (ie, only has template skeleton, but no details inside it)
2. Duplicate of existing open issues.

As an example, see below recent empty issues that were filed with no details that we closed due to lack of information:

#117521
#118251
#118241
#118235
#118225

This filter for duplicates that we closed as applicable with r: duplicate label.

Proposal

1. To avoid OP filing an empty issue, if we could introduce required fields , so that we will have enough details to act on the filed issue. As an example:

[REQUIRED] in front of each section or atleast for code sample and logs

2. A Duplicate check section, something like below:

3. Improving the title / text of below template specifically:

To something like Report a bug with description Think you found a bug in the framework / SDK? Report it here., so that this will make OP to only file genuine framework related bugs and hopefully not general issue which may not be related to the framework. For that, we can direct them to I want help writing my application option.

Templates

• Migrate "Activation / Installing Flutter" issue template to Github forms #119914
• Migrate the "Bug report" issue template to Github forms #119918
• Migrate the "Feature request" issue template to Github forms #119919
• Migrate the "Non-speed related performance issues" issue template to Github forms #119920
• Migrate the "Missing frames / speed related performance issues" issue template to use Github forms #119921
• Migrate the "CI infrastructure issues" issue templates to use Github forms #119922
• Make flutter/flutter new issue template for 1p plugins #117750

Concluding note

We understand that above proposal is subject to how OP would look at it and whether they would make use of it or not depending on their approach to file the issue, but it will help to reduce the noise of the issues that would most likely get closed as invalid / duplicates and we would see more genuine framework related bugs.

[khyati82]

CC @Hixie

[Hixie]

Please feel absolutely empowered to adjust the templates as you see fit.

[ricardoamador]

This is not an infra issue. Any team can update templates in the repositories.

[huycozy]

Closing this issue as all templates have been migrated.