[wp-meta] [Making WordPress.org] #3567: Redirect my-patches and my-patches/all URLs for updated reports

Making WordPress.org noreply at wordpress.org
Tue Apr 10 15:51:52 UTC 2018

#3567: Redirect my-patches and my-patches/all URLs for updated reports
 Reporter:  stevenlinx  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  normal      |  Milestone:
Component:  Trac        |   Keywords:
 There are inconsistencies between "`my-patches` | `my-patches/all`" pair
 and "`my-comments` | `my-comments/all`" pair

 The "`my-comments` | `my-comments/all`" pair work as they should, pointing
 to report {53} and {54} respectively:


 The "`my-patches` | `my-patches/all`" pair need to be updated:


 The respective "patches" reports in question are report {25} and {29}.

 Previously, both report {25} and report {29} were duplicates and show open
 tickets. However, report {29} already has the title "Open Tickets with My
 Patches", so if either one of them need to be updated, updating report
 {25} to include both open & closed tickets is more appropriate.

 After I raised the issue of duplicate reports, one of the meta admins
 acknowledged the issue and has updated the content of report {25} to
 include both open & closed tickets.

 Currently, `my-patches` still points to report {25} when it should be
 redirected to report {29} (open tickets). `my-patches/all` currently does
 not point to any report and should be redirected to the updated report
 {25} (open & closed tickets).

 As a result, the remaining task is to redirect the URLs:

    `my-patches` => report {29} (open tickets)

    `my-patches/all` => report {25} (open & closed tickets)

Ticket URL: <https://meta.trac.wordpress.org/ticket/3567>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list