Creating Core ticket
WordPress is an open-source CMS platform that is used by millions of websites around the world. It’s free and available under a GPLv2 (or later) license. There are thousands of contributors who help to make it better every day, which means that anyone can add new features or fix bugs in the code. If you have found a bug or want to suggest a new feature, please create a ticket at the WordPress Trac.
Make sure to search for current tickets before creating a new ticket. If your ticket has been created and it is not the first time you have submitted it, please check the progress of the previous tickets and participate in them.
There are many reasons why WordPress recommends this approach:
- It helps the community better understand the problems that need to be solved.
- It helps the community to prioritize tickets and ensure that they are being addressed in a timely manner.
- It provides additional context so the community can better address your issue.
- It ensures that all feedback is captured in one place, which will help the community provide a more accurate response.
Use keywords that are relevant to the ticket while searching; additionally, choose filters that separate out the tickets based on components.
Creating a ticket
Go to https://core.trac.wordpress.org/newticket for a new ticket
The details for creating new Trac tickets are as follows:
Summary: Provide the title of the Trac ticket.
Description: Explain the issue in detail. Include as much relevant information as possible. You can also upload screenshots directly to Trac—tools like CloudApp or Lightshot work well, but any reliable service is fine.
Type: Choose whether this is a bug, enhancement, or feature request.
Version: Specify the WordPress version where the issue occurs (e.g., trunk is currently at 6.7 and will move to 6.8 after release).
Workflow Keywords (commonly used):
- Reporter Feedback: More details needed from the reporter.
- Needs Patch: A patch is required.
- Has Patch: A patch has already been submitted.
A full list of keyword descriptions is available online. If you’re unsure about a keyword, simply leave it out—experienced contributors will apply the correct ones.
Priority: This is usually set by core committers. It’s best to skip it.
Component: Examples include:
- Bundled Themes: Default themes shipped with core.
- Post Formats: Issues related to post formats.
- Widgets: Issues related to widgets.
You can refer to the full component list for more options. If you’re uncertain, leave this blank and someone more experienced will update it.
References: