Bug Reports

7:49 pm on January 29, 2014
Bug Reports
WordPress uses open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. software called TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to manage bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. reports and tasks. If you are looking to report a bug, please ​head on over.
There are many ways to contribute. We have a detailed contributor handbook to help get you started. If you want to get started quickly, try one of the Getting Started reports below — test a patch, or grab a bug and see if you can reproduce the problem it describes.
If you have encountered a security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have. in WordPress, please contact security at wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. For more, see our ​Security FAQ.
Trac Ticketticket Created for both bug reports and feature development on the bug tracker. Reports
Latest Tickets
Active Tickets
Trac Timeline
Ticket Graphs
Browse Source
Milestones
Me
Create a Ticket
Please log in to see your tickets.
Tickets by Release
Next Major Release (6.6)
Grouped by workflow
Next Minor Release
Grouped by workflow
Future Releases
Grouped by workflow
Tickets by Topic
Tickets by Component
Select a componentAdministrationApplication PasswordsAutosaveBootstrap/LoadBuild/Test ToolsBundled ThemeCache APICanonicalCharsetCommentsCron APICustomizeDatabaseDate/TimeEditorEmbedsEmojiExportExternal LibrariesFeedsFilesystem APIFormattingGalleryGeneralHTML APIHTTP APIHelp/AboutI18NImportLogin and RegistrationMailMediaMenusNetworks and SitesOptions, Meta APIsPermalinksPings/TrackbacksPluginsPost FormatsPost ThumbnailsPosts, Post TypesPrivacyQueryQuick/Bulk EditREST APIRevisionsRewrite RulesRole/CapabilityScript LoaderSecurityShortcodesSite HealthSitemapsTaxonomyText ChangesThemesTinyMCEToolbarUpgrade/InstallUploadUsersWidgetsWordPress.org SiteXML-RPC
Tickets by Focus
Select a focusaccessibilityadministrationcoding-standardscssdocsjavascriptmultisiteperformanceprivacyrest-apirtltemplateui
Design your own query
Getting Started
Patches Needing Testing
Needs Unit Tests
Tickets without a Patch
Good First Bugs for New Contributors
Tickets Needing Feedback
Tickets awaiting review
Tickets that are ancient and inactive
Tickets requesting developer feedback
Tickets requesting design feedback
Other Workflow Reports
• Tickets needing a patch (needs-patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.)
• Tickets with a patch (has-patch)
• Critical tickets (blockers)
• Commit candidates (commit)
• Tickets with a suggestion to close (2nd-opinion or close)
• Tickets that should be considered early in a release cycle (early)
• Closed tickets needing a secondary review
• Mobile — Tickets flagged by the WordPress mobile apps team
• WordPress.org — Importer plugins, old default themes, etc.
• Meta Trac for the WordPress.org site itself