The mysteries of mediawiki-bugzilla have been solved

Already four years ago I lamented the lack of documentation for the 
mediawiki-bugzilla extension. I could not for the life of me understand 
how to create more complex queries. Yesterday Dave Miller from Bugzilla 
advised me on the topic and now everything is clear!

Let's look at an example from our wiki:

<bugzilla>
    {
        "status": ["NEW", "REOPENED", "ASSIGNED"],
        "n1": "1",
        "f1": "keywords",
        "o1": "anywords",
        "v1": "needsDevEval needsUXEval",
        "f2": "keywords",
        "o2": "allwords",
        "v2": "easyHack difficultyBeginner topicQA",
        "order": "bug_id"
    }
</bugzilla>

This is constructed based on a custom search in the advanced search 
interface of Bugzilla. All the parameters have been picked from the 
generated search URL. The meanings are:

(n)ot
(f)ield
(o)perator
(v)alue

In the above query, we do not want reports with either needsDevEval or 
needsUXEval. We do want reports with all of the words easyHack, 
difficultyBeginner and topicQA. The Not parameter matches the Not 
checkbox in the custom search section in Bugzilla.

After seeing this conversation, Chris Peterson mentioned that he has 
documented many of the field and operator names we can use: 
https://wiki.mozilla.org/User:Cpeterson
The column "Query field" contains parameters we can use in the wiki.

All of our easy hack pages in the wiki have been updated to provide more 
accurate queries.

Now you can all have fun in the wiki creating intricate queries to your 
heart's content. Feel free to contact me, if you need help.

Ilmari