WordPress ticket classification

Large-category classification for Gutenberg GitHub issues and WordPress Core Trac tickets, stored in a reusable SQLite database.

Gutenberg classified
32,144
15,217 comments stored
Core classified
64,951
304,500 comments stored
Gutenberg confidence
22,081 high
3,201 low-confidence rows
Core confidence
64,951 high
0 low-confidence rows

Gutenberg GitHub issues

Bugs
15,801
49% of all tickets · 1,957 open
Enhancements
8,434
26% of all tickets · 2,975 open
Other / unclear
3,201
10% of all tickets · 172 open
Documentation
1,083
3% of all tickets · 141 open
Support / questions
1,052
3% of all tickets · 11 open
Feature requests
678
2% of all tickets · 60 open
Tasks / maintenance
658
2% of all tickets · 88 open
Flaky tests
650
2% of all tickets · 87 open
Accessibility
430
1% of all tickets · 58 open
Performance
126
0% of all tickets · 26 open
Security
31
0% of all tickets · 2 open
Gutenberg category timeline Tickets created per year, split by primary category. Bugs Feature requests Enhancements Tasks / maintenance Documentation Support / questions Flaky tests Accessibility Performance Security Other / unclear 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 4,998 tickets
Gutenberg issues by category Primary category across all cached WordPress/gutenberg issues. Bugs 15,801 Enhancements 8,434 Other / unclear 3,201 Documentation 1,083 Support / questions 1,052 Feature requests 678 Tasks / maintenance 658 Flaky tests 650 Accessibility 430 Performance 126 Security 31
Gutenberg open backlog by category Dark bars are currently open issues; pale bars are total issues in that category. Bugs 1,957 open / 15,801 total Enhancements 2,975 open / 8,434 total Other / unclear 172 open / 3,201 total Documentation 141 open / 1,083 total Support / questions 11 open / 1,052 total Feature requests 60 open / 678 total Tasks / maintenance 88 open / 658 total Flaky tests 87 open / 650 total Accessibility 58 open / 430 total Performance 26 open / 126 total Security 2 open / 31 total

Gutenberg is mainly concentrated in bugs (49%), enhancements (26%), other / unclear (10%).

The current open set is led by enhancements (2,975 open), bugs (1,957 open), other / unclear (172 open).

WordPress Core Trac tickets

Bugs
44,740
69% of all tickets · 4,664 open
Enhancements
16,067
25% of all tickets · 2,941 open
Feature requests
2,357
4% of all tickets · 524 open
Tasks / maintenance
1,787
3% of all tickets · 94 open
Core category timeline Tickets created per year since 2003, split by primary category. Bugs Feature requests Enhancements Tasks / maintenance 2004 2006 2008 2010 2012 2014 2016 2018 2020 2022 2024 2026 4,392 tickets
WordPress Core tickets by category Primary category across all Core Trac tickets in the database. Bugs 44,740 Enhancements 16,067 Feature requests 2,357 Tasks / maintenance 1,787
Core open backlog by category Dark bars are currently open tickets; pale bars are total tickets in that category. Bugs 4,664 open / 44,740 total Enhancements 2,941 open / 16,067 total Feature requests 524 open / 2,357 total Tasks / maintenance 94 open / 1,787 total

Core is mainly concentrated in bugs (69%), enhancements (25%), feature requests (4%).

The current open set is led by bugs (4,664 open), enhancements (2,941 open), feature requests (524 open).

Local SQLite database: /Users/admin/wordpress_ticket_classification/wordpress_tickets.sqlite. Classification version: 2026-06-12.1.

Published CSVs: Gutenberg summary, Core summary, category trend.

Core uses Trac type as the strongest signal. Gutenberg uses issue type labels first, then title/body/comment text. Secondary facets preserve accessibility, performance, security, duplicate, stale, needs-info, and has-patch signals.