WordPress Core is built by thousands of contributors working together on an open-source platform. With that scale comes complexity: at any given time, there are thousands of tickets in WordPress Trac reporting bugs, requesting features, and proposing enhancements.
You can find detailed information about how the WordPress community manages WordPress Core tickets in the Core Contributor Handbook
Triage—the process of reviewing, organizing, and prioritizing these tickets—helps contributors focus on the work that matters most. Right now, the WordPress community is running regular bug scrubs to prepare for WordPress 7.0.
But triaging tickets for WordPress Core nowadays require to deal with a UI that hasn’t changed much since 2006, and getting the information you need to make good triage decisions means scrolling through walls of comments, hunting for milestone changes, and trying to figure out who’s who in the conversation—especially challenging for tickets with long discussion histories spanning multiple releases.
That’s the problem I set out to help with WP Trac Triager, a Chrome extension I published last week.
Table of Contents
Why This Extension Exists
During conversations in the WordPress Test Team Training Program, we discussed several times how triaging Trac tickets effectively requires context that’s buried in the UI.
The Trac interface itself is hard to change—any UI improvements have historically been difficult to implement. So I thought, OK, let’s do it “from the outside” with a Browser extension 😎
What It Does
WP Trac Triager adds a smart sidebar to every Trac ticket with all the context you need in one place.



Here’s what you get:
Smart Timelines & History
Keyword Change Timeline
See the complete visual history of all keyword additions and removals. Changes are color-coded—green for additions, red for removals, orange for mixed changes. Hover over any keyword to see its description and usage guidelines from the WordPress Core Handbook. Every entry links directly to the comment where the change happened.
Milestone History Timeline
Track every milestone change in a vertical timeline. Each entry shows who made the change, when, and what it changed from/to.
Universal Role Recognition
Role Badges for Everyone
Every commenter gets a role badge—Project Lead, Core Committer, Component Maintainer, Individual Contributor, etc. At a glance, you can identify the ticket reporter, which committers have weighed in, and which maintainers are involved—instantly understanding who has authority to make decisions and who you should follow up with.
Fully Customizable Sidebar
The sidebar is yours to configure:
- Drag & Drop Reordering — Arrange sections in your preferred order via the Settings page
- Show/Hide Toggles — Hide sections you don’t use to declutter your view
- Persistent Preferences — Settings sync across all your devices via Chrome
- Locked Critical Info — Quick Info section always stays visible at the top
Rich Information Sections
The sidebar organizes everything you need:
- Quick Info — Ticket summary, reporter, milestone, priority, component
- WordPress Release Schedule — Next milestone dates with countdown timer
- Recent Comments — Last 3 comments with role context and quick navigation to the full discussion
- Milestone History — Visual timeline of all milestone changes
- Keyword Change History — Complete timeline of keyword additions/removals
- Component Maintainers — Contact info with links to profiles
- TRAC Keywords — Explanations for all keywords based on the Core Handbook
All of this appears inline, right where you need it, without leaving the ticket page.
Who It’s For
I think this extension is helpful for both experienced triagers and new contributors:
- Experienced triagers who want to work more efficiently and catch details they might otherwise miss, especially during systematic bug scrubs and milestone planning.
- New contributors who are learning how to triage properly. By surfacing the right information automatically, it teaches you what to look for and why it matters.
Try It Out
- Install: Chrome Web Store
- Source: GitHub repo (Issues are welcome)
If you’re involved in WordPress Trac triage—or want to start contributing—give it a try. It won’t change Trac itself, but it’ll make your life a lot easier while you’re there.
WP Trac Triager was mentioned on WP Weekly (see WP Weekly 280 – Builder’s AI) , The Gutenberg Times (see Block Theme Guide, AI Galore, Icon Block, WordPress 7.0 — Weekend Edition 357) and WP-Content (see #259 – WP Engine Amended Complaint, Bertha.ai Exits Repository, New AI Site Builder, Plugin Collaboration Opportunity)

Leave a Reply