[wp-trac] [WordPress Trac] #64733: Tickets menu on Changeset pages redirects to make core/reports/ page instead of opening tickets menu
WordPress Trac
noreply at wordpress.org
Thu Feb 26 10:32:36 UTC 2026
#64733: Tickets menu on Changeset pages redirects to make core/reports/ page
instead of opening tickets menu
--------------------------+------------------------------
Reporter: hbhalodia | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
--------------------------+------------------------------
Old description:
> While browsing WordPress Core Trac, specifically on a changeset page such
> as:
>
> https://core.trac.wordpress.org/changeset/<id>
>
> Clicking on the “Tickets” menu item in the top navigation does not open
> the expected Trac overlay/dropdown menu. Instead, it redirects the user
> to:
>
> https://make.wordpress.org/core/reports/
>
> This behavior is inconsistent with the navigation pattern on other Core
> Trac pages, where clicking “Tickets” opens the overlay menu allowing
> users to select options such as:
>
> 1. Latest Tickets
> 2. Active Tickets
> 3. Create a Ticket .. etc
>
> Steps to Reproduce:
>
> Go to any changeset page on Core Trac (e.g., /changeset/<id>).
>
> Click on the “Tickets” menu item in the top navigation.
>
> Observe that it redirects to the Make/Core reports page instead of
> opening the Trac overlay menu.
>
> Expected Behavior:
>
> When clicking the “Tickets” menu item on a changeset page, it should
> behave consistently with other Core Trac pages and open the Trac
> overlay/dropdown menu, allowing users to choose their preferred ticket
> view.
>
> Actual Behavior:
>
> The link redirects to https://make.wordpress.org/core/reports/, breaking
> navigation consistency within Core Trac.
>
> Impact:
>
> Inconsistent navigation experience across Core Trac. Breaks user
> expectations when switching between changesets and ticket views.
>
> **PS: Used AI model to create a description and Subject line of the
> ticket. Also, was not having an idea where to report this, so created a
> trac ticket. I would be happy to create it on other place, where this
> should actually be.**
>
> Demo Screencast - https://app.godam.io/web/video/bgdmm5pkgf
New description:
While browsing WordPress Core Trac, specifically on a changeset page such
as:
`https://core.trac.wordpress.org/changeset/<id>`
Clicking on the “Tickets” menu item in the top navigation does not open
the expected Trac overlay/dropdown menu. Instead, it redirects the user
to:
https://make.wordpress.org/core/reports/
This behavior is inconsistent with the navigation pattern on other Core
Trac pages, where clicking “Tickets” opens the overlay menu allowing users
to select options such as:
1. Latest Tickets
2. Active Tickets
3. Create a Ticket .. etc
Steps to Reproduce:
Go to any changeset page on Core Trac (e.g., `/changeset/<id>`).
Click on the “Tickets” menu item in the top navigation.
Observe that it redirects to the Make/Core reports page instead of opening
the Trac overlay menu.
Expected Behavior:
When clicking the “Tickets” menu item on a changeset page, it should
behave consistently with other Core Trac pages and open the Trac
overlay/dropdown menu, allowing users to choose their preferred ticket
view.
Actual Behavior:
The link redirects to https://make.wordpress.org/core/reports/, breaking
navigation consistency within Core Trac.
Impact:
Inconsistent navigation experience across Core Trac. Breaks user
expectations when switching between changesets and ticket views.
**PS: Used AI model to create a description and Subject line of the
ticket. Also, was not having an idea where to report this, so created a
trac ticket. I would be happy to create it on other place, where this
should actually be.**
Demo Screencast - https://app.godam.io/web/video/bgdmm5pkgf
--
Comment (by sabernhardt):
This report belongs on [https://meta.trac.wordpress.org/newticket Meta
Trac], under the Trac component.
The behavior is inconsistent, but overriding the link semantics to bring
content from the target page into the current page should be more
unexpected than a link acting as a link on the changeset pages.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64733#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list