Available Reports

Compose a new ticket query by selecting filters and columns to display.

• All active tickets
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• All active tickets, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets slated for the next minor release
• Sort by component, type, summary, fixed
• Accepted tickets have an '*' appended to their owner's name
• Tickets marked as fixed are included below for reference

• Active tickets slated for the next minor release, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets slated for the next major release
• Sort by component, severity, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets slated for the next major release, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets slated for future releases or with no assigned milestone
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets slated for future releases or with no assigned milestone, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Commit Candidates, grouped by milestone
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that need feedback or reviewing from the WordPress developers or regular bug wranglers (keywords: dev-feedback, needs-review)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that need feedback from whoever reported the ticket, usually because we're failing to reproduce (keyword: reporter-feedback)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name
• Yellow: Last modified more than a Month ago, Red: Last Modified more than 6 Months ago

• Tickets that need unit tests (keywords: needs-unit-tests)
• In some cases, these tickets have patches but need tests in order to be committed)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that have a patch and now need testing to make sure the patch works and doesn't introduce new bugs (keywords: has-patch, needs-testing)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that are explicitly marked as needing early attention in the next major release (keyword: early)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that have a patch and are explicitly marked as needing extra testing
• Sorted by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that lack an attachment or are explicitly marked as needing a patch (keyword: needs-patch)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that bug wranglers suspect are dups, and invalid/wontfix suggestions that could use a second opinion (keyword: dup, close)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Potential blockers for releases
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

Requirements to be listed here: Milestoned for the next major release and one of the following: 1) highest omg bbq priority 2) critical/blocker severity 3) has the blocked keyword.

• All tickets opened in the last two months
• Sort by created
• Highlighted tickets are still 'Awaiting Review'

• Tickets that have been active in the past two weeks
• Sort by modified
• Accepted tickets have an '*' appended to their owner's name

• Tickets that have one follower or more
• Sort by votes, component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that you've accepted, that were assigned to you or a component you own, or that you've reported
• Sort by milestone, component, type, summary
• Accepted tickets have an '*' appended to their owner's name

_{Hidden feature: /my-tickets?USER=$name pulls up someone else's ticket list.}

• Tickets that you've contributed a patch to
• Sort by milestone, component, type, summary
• Accepted tickets have an '*' appended to their owner's name

_{Hidden feature: /my-patches?USER=$name pulls up someone else's patch list.}

Grouped by component. The following components are tracked here:

• Import: The core importers, now in the plugins repository
• Themes: previously bundled themes (Kubrick, Classic), now in the themes repository
• WordPress.org: Tickets related to the workings of the wordpress.org site

Tickets that have been reviewed by trusted Bug Wranglers and have up-to-date patches and are ready to be considered for inclusion into the WordPress core.

This report highlights any tickets which the current user has added patches on, yet the ticket remains open.

By default, this report shows tickets for the current user, however, you may view other users' patches using URL like: https://core.trac.wordpress.org/report/29?USER=username, where username should be replaced with a WordPress.org username.

Colored rows are those where the ticket has been marked as needing a patch.

• Active tickets with a focus on $FOCUS
• Grouped by workflow and sorted by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets in the $COMPONENT component
• Grouped by workflow and sorted by type, summary
• Accepted tickets have an '*' appended to their owner's name

• Many of these tickets need to be triaged and eventually punted
• Active enhancement and feature request tickets slated for the next major release, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name
• Default owners in a component are shown in parentheses if the ticket status remains 'new'

• Tickets that lack an attachment or are explicitly marked as needing feedback (needs-design-feedback, ux-feedback or ui-feedback)
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that explicitly marked as needing codex updates (needs-codex / needs-user-docs)
• Remove the keyword once the Docs is updated
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name
• Only tickets for the current stable branch and higher are included.

• Tickets that explicitly marked as needing unit tests (needs-unit-tests), or tickets in the Unit Tests component
• Remove the keyword once the unit tests are committed
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

Tickets in the Awaiting Review milestone.

Customize the query here: ​http://core.trac.wordpress.org/query?milestone=Awaiting+Review.

These tickets are split into four groups:

• Bug reports without any comments at all
• Bug reports without any activity from someone other than the author
• Bug reports without any comments from someone other than the author (thus excluding components and other property changes)
• Enhancements that need a reply
• Tickets that meet any of these criteria, but were themselves opened by a bug gardener

• Tickets that explicitly marked as being related to one of the mobile apps
• Provide a keyword of "mobile" to show up on this list

Tickets not modified in the past 2.5 years. Once this report is emptied, we'll adjust the threshold to 2 years, and so on.

These tickets have been marked as being a "good first bug" for new contributors.

First bugs aren't necessarily "easy," though some are. These bugs are meant to be well-contained. They are designed to help get you familiar with WordPress core code, processes, and contributing, not send you down a rabbit hole for days on end. Whoever marked the ticket likely explained in the ticket why they did so, giving you a good starting point from which to work.

The person who marked the ticket as a "good first bug" — as well as other members of the community — will help you through this ticket by providing feedback along the way. Start by getting a handle on the problem, verifying that you can reproduce it, drawing up a plan of attack, and then creating a patch.

The ​Core Contributor Handbook should have some good reference materials for you, including ​an overview of the codebase, ​coding standards, ​how we use our bug tracker, and various tutorials and guides like setting up a development environment and creating patches.

If you're not a contributor who is just starting out, please find one of the hundreds of other bugs to patch!

If this report is running low or nothing catches your eye, try this report of tickets that need a patch. If you like unit tests, you can check out how automated testing is set up ​in the handbook, then browse the tickets that need unit tests. Or, if you want to contribute by testing patches, here are some patches that have been marked as specifically needing testing.

• Tickets marked as needs-patch, but have never had a patch uploaded
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

Please see the ​Bug Gardening page in the Core Contributor Handbook for a guide on how to help with tickets in this report.

A ticket can be closed by anyone, but milestones can only be removed by bug gardeners. This allows for secondary review of ticket closures by another contributor, who then needs to remove the milestone.

If there are any tickets on this report, they need this secondary review from a bug gardener.

This applies to tickets closed as invalid, wontfix, maybelater, worksforme, or duplicate. Only bug gardeners can close a ticket as fixed, as this is typically done via a commit. For more on ticket resolutions and properties, see ​the handbook.

• Open tickets I'm watching
• Sorted by last modified

_{Hidden feature: /my-favorites?USER=$name pulls up someone else's ticket list.}

• All tickets I'm watching (opened and closed)
• Sorted by last modified

_{Hidden feature: /my-favorites/all?USER=$name pulls up someone else's ticket list.}

• Open tickets I've participated in (See all tickets, including closed)
• Sorted by last modified

_{Hidden feature: /my-comments?USER=$name pulls up someone else's ticket list.}

• All tickets I've participated in (open and closed) (See only open tickets)
• Sorted by last modified

_{Hidden feature: /my-comments/all?USER=$name pulls up someone else's ticket list.}

• Bugs that have been reported against trunk.
• Excludes tickets marked close or reporter-feedback.

• Active tickets slated for the next major release
• Grouped by the contributor who changed the ticket's milestone
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Tickets that you own, that were assigned to you, accepted by you, reopened, or under review by you
• Sorted by status, milestone, component, modified date

_{Hidden feature: /?USER=$name pulls up someone else's ticket list.}

Testing ​https://meta.trac.wordpress.org/ticket/5453

• Active tickets slated for the next minor release, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

• Active tickets slated for the next minor release, workflow oriented
• Sort by component, type, summary
• Accepted tickets have an '*' appended to their owner's name

eg; https://core.trac.wordpress.org/report/66?COMPONENT=Users

See ​https://meta.trac.wordpress.org/ticket/7662

• Tickets that are bugs and
  • Need feedback from whoever reported the ticket, usually because we're failing to reproduce (keyword: reporter-feedback)
  • Don't have a patch, don't need a patch, and need testing

20 most active tickets in the last 7 days with at least 4 participants (Excluding bots)