Why open issues grew, stalled, then started declining
Switch between all issues, bugs, and feature requests at any point while scrolling.
All Gutenberg issues
All WordPress/gutenberg issues in the five-year inventory, excluding pull requests.
Timeline
New and Closed Issues
Where The Decline Comes From
Reporting Trend
Short Discussion
The strongest signal is fewer new issues. In the full-quarter averages, new issues fell from 967.6 per quarter during growth to 534.0 during decline. That is a large inflow change, and it starts before the biggest cleanup pulse.
Closures also matter. The monthly net-flow chart shows several months where closures exceeded new issues, especially late 2025 and the partial June 2026 window. That means the falling open count is partly backlog cleanup, not only fewer reports.
Fewer people are filing issues on GitHub. Unique creators fell from 333.0 to 203.2 per quarter, and first-time creators fell from 121.3 to 62.5. So the reporting funnel itself looks smaller.
The cautious interpretation: GitHub issue activity is lower, and old backlog is being cleaned up. That does not prove Gutenberg has fewer real-world problems; it means fewer problems are being reported or managed as open GitHub issues, while maintainers are also closing older threads.
Bug-labeled Gutenberg issues
Issues with the current GitHub label "[Type] Bug". Labels are current API fields, not historical labels at creation time.
Timeline
New and Closed Issues
Where The Decline Comes From
Reporting Trend
Short Discussion
The strongest signal is fewer new bug reports. In the full-quarter averages, new bug reports fell from 343.5 per quarter during growth to 236.5 during decline. That is a large inflow change, and it starts before the biggest cleanup pulse.
Closures also matter. The monthly net-flow chart shows several months where closures exceeded new bug reports, especially late 2025 and the partial June 2026 window. That means the falling open count is partly backlog cleanup, not only fewer reports.
Fewer people are filing issues on GitHub. Unique creators fell from 164.1 to 128.2 per quarter, and first-time creators fell from 64.7 to 48.5. So the reporting funnel itself looks smaller.
The cautious interpretation: GitHub issue activity is lower, and old backlog is being cleaned up. That does not prove Gutenberg has fewer real-world problems; it means fewer problems are being reported or managed as open GitHub issues, while maintainers are also closing older threads.
Feature-request Gutenberg issues
Issues with the current GitHub label "[Type] Enhancement", used here as Gutenberg's feature-request time-series view.
Timeline
New and Closed Issues
Where The Decline Comes From
Reporting Trend
Short Discussion
The strongest signal is fewer new feature requests. In the full-quarter averages, new feature requests fell from 291.1 per quarter during growth to 181.8 during decline. That is a large inflow change, and it starts before the biggest cleanup pulse.
Closures also matter. The monthly net-flow chart shows several months where closures exceeded new feature requests, especially late 2025 and the partial June 2026 window. That means the falling open count is partly backlog cleanup, not only fewer reports.
Fewer people are filing issues on GitHub. Unique creators fell from 128.2 to 86.2 per quarter, and first-time creators fell from 50.1 to 28.5. So the reporting funnel itself looks smaller.
The cautious interpretation: GitHub issue activity is lower, and old backlog is being cleaned up. That does not prove Gutenberg has fewer real-world problems; it means fewer problems are being reported or managed as open GitHub issues, while maintainers are also closing older threads.
Optional: what sampled closures looked like
The open count declined partly because old issues were cleaned up.
Recent closures more often looked like targeted fixes or active duplicate consolidation. Old closures had more stale, superseded, scope-shift, and "not evidence of an active bug" signals. So the decline is not the same thing as "all old problems were solved."
That is why the decision answer is mixed: fewer GitHub reports are coming in, and real fixes exist, but backlog pruning is a major part of the visual drop.
Methods, caveats, and source files
- Fetched 32,135 public issue records from the GitHub REST API with authenticated access on 2026-06-11.
- Quarterly and monthly charts exclude pull requests. First and last quarters are partial.
- Labels and state reasons are current API fields, not historical labels at creation time.
- Qualitative coding used deterministic samples: 45 created issues per period, 45 old decline closures, and 30 recent decline closures.
- No off-GitHub channels such as Trac, support forums, Slack, or Make/Core were crawled.