[wp-meta] [Making WordPress.org] #7935: Core Trac Workflow Keywords Issue

[Making WordPress.org]

#7935: Core Trac Workflow Keywords Issue
--------------------------+---------------------
 Reporter:  SirLouen      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:
Component:  Trac          |  Resolution:
 Keywords:  needs-patch   |
--------------------------+---------------------

Comment (by SirLouen):

 Replying to [comment:2 dd32]:
 > perhaps the solution is to use existing built reports rather than
 freeform queries.
 >
 > This needs to be discussed in #core and a direction formalised before
 any action can be taken on this ticket though.

 The problem with this, is that it doesn't provide the opportunity to check
 for certain types of tickets around `needs-testing` which happens to be a
 "key" keyword. For example, I was willing recently to review tickets that
 had both `needs-testing` and `needs-testing-info` at the same time
 specifically and was completely impossible.

 In fact, I have to admit to you that this happens to be the most critical
 combination of keywords. The other one, I put as an example, was just
 another case of this inconvenience, but not as problematic as these two.

 There are 2 solutions from my perspective:

 1. Repairing the Trac query system, either by adding exact matches with
 quotes or the liking, or by just considering each exact keyword for each
 match between spaces

 2. The simplest one that requires less coding: renaming either needs-
 testing or needs-testing info to avoid having them contained in each
 other. Just a little change like `need-testing-info` will also do the
 trick and I feel that I will not be less human-readable.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7935#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org