Repository navigation
[Triage/Infra] Consolidate 09_feature.yml umbrella template to free up issue chooser slot #190315
Description
Background
GitHub limits the repository issue chooser menu to a maximum of 10 templates (.github/ISSUE_TEMPLATE/*.yml). flutter/flutter is currently at the hard cap of 10 templates:
01_activation.yml02_bug.yml03_feature_request.yml04_performance_others.yml05_performance_speed.yml06_infrastructure.yml07_design_doc.yml08_first_party_packages.yml09_feature.yml10_google3_bug.yml
Proposal
We propose consolidating 09_feature.yml ("Create an umbrella issue") into 03_feature_request.yml (or consolidating 04_performance_others.yml and 05_performance_speed.yml into a single Performance template).
An audit of flutter/flutter, flutter/website, and historical issue links confirms:
09_feature.ymlhas 0 code references and 0 external URL references across the organization.- Umbrella issues (
☂️ <Feature Title>) can easily be documented as a recommended title convention inside03_feature_request.yml.
Freed capacity in the 10-template chooser menu can then accommodate emerging needs (such as dedicated WebAssembly / framework feedback forms).
Suggested Action
We can submit a clean PR to remove 09_feature.yml and add umbrella title guidance to 03_feature_request.yml.
Activity
kevmoo commentedon Jul 30, 2026
CC @stuartmorgan-g @goderbauer
stuartmorgan-g commentedon Jul 31, 2026
If we need to eliminate some templates we should probably gather data about how much use the various templates get (by looking for specific header text, for instance). Taking
08_first_party_packages.ymlas an example, we added it because we wanted to avoid round-trips during triage to ask for information we very frequently need for those issues, but in practice only about 12% ofpackageissues filed in the last year actually used that template, because most people just pick "bug" or "feature request" instead, so the utility of having the specialized template is low. Anecdotally, the performance template is frequently used incorrectly, so I'm not sure how much that's buying us either.(By the same token though, the utility of adding new specialized templates may well also be low unless we have a specific way to funnel people directly to them.)
kevmoo commentedon Jul 31, 2026
Recommendations
Drop
01_activation.yml(Frees Slot#1)02_bug.yml.Consolidate
09_feature.ymlinto03_feature_request.yml(Frees Slot#2)☂️ <Title>convention inside03_feature_request.yml.Merge
04_performance_others.ymland05_performance_speed.ymlinto 1 Performance template (Frees Slot#3)Key Data Findings
08_first_party_packages.yml: Of ~750 package bug reports filed in the last year, 380 (~50.3%) used this template, while ~370 used02_bug.yml. Usage has grown significantly over previous years.04&05): Data supports Stuart's observation. Combined filings are extremely low (17 total issues in the last year across both forms). Manual audit shows:01_activation.yml: Unused (0 filings in the past year, 14 all-time).09_feature.yml: Very low volume (21 filings in the last year).Template Usage Data (Past 12 Months)
Based on form header markers and auto-applied labels across all 6,551 issues created since Aug 1, 2025:
02_bug.yml06_infrastructure.yml03_feature_request.yml08_first_party_packages.yml07_design_doc.yml10_google3_bug.yml09_feature.yml05_performance_speed.yml04_performance_others.yml01_activation.ymlkevmoo commentedon Jul 31, 2026
@stuartmorgan-g RE
(By the same token though, the utility of adding new specialized templates may well also be low unless we have a specific way to funnel people directly to them.)- I'm going to create a short link to point folks to the template. Going to avoid linking to it directly so it's easy to update later and delete.goderbauer commentedon Jul 31, 2026
cc @justinmc is maybe the better POC for this than me.
flutter-triage-bot commentedon Jul 31, 2026
The
fyi-infralabel is redundant with theteam-infralabel.jtmcdole commentedon Aug 3, 2026
This is not team-infra. This is more "team-admin" .
justinmc commentedon Aug 3, 2026
Is 09_feature even being used? I don't see it when I go to create a new issue: https://github.com/flutter/flutter/issues/new/choose
If not then I definitely think it can be removed!
kevmoo commentedon Aug 3, 2026
09_feature.yml is the sole template out of all ten files specifying a project attachment: projects: ["flutter/82"].
project flutter/82 returns HTTP 404 (Not Found)
When GitHub renders /issues/new/choose, its backend schema validator fails to bind target project flutter/82. Rather than reporting a public UI error, GitHub silently suppresses and drops the failing template from the rendered chooser.
kevmoo commentedon Aug 3, 2026
I'm going to steal
#9for my use since it's broken anyway and duplicated w/#03[Infra] Replace defunct umbrella template with Wasm issue form (flutt…
github-actions commentedon Aug 17, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.