Commit a69f0f97 authored by lpsolit%gmail.com's avatar lpsolit%gmail.com

Doc patch for bug 244239: Add group-based pronouns to query - Patch by me, r=justdave

parent bc040aab
......@@ -450,17 +450,26 @@
<section id="pronouns">
<title>Pronoun Substitution</title>
<para>
Sometimes, a query needs to compare a field containing
a user's ID (such as ReportedBy) with
a user's ID (such as the user running the query or the user
to whom each bug is assigned). When the operator is either
"equals" or "notequals", the value can be "%reporter%",
"%assignee%", "%qacontact%", or "%user%." The user pronoun
Sometimes, a query needs to compare a user-related field
(such as ReportedBy) with a role-specific user (such as the
user running the query or the user to whom each bug is assigned).
When the operator is either "equals" or "notequals", the value
can be "%reporter%", "%assignee%", "%qacontact%", or "%user%".
The user pronoun
refers to the user who is executing the query or, in the case
of whining reports, the user who will be the recipient
of the report. The reporter, assignee, and qacontact
pronouns refer to the corresponding fields in the bug.
</para>
<para>
Boolean charts also let you type a group name in any user-related
field if the operator is either "equals", "notequals" or "anyexact".
This will let you query for any member belonging (or not) to the
specified group. The group name must be entered following the
"%group.foo%" syntax, where "foo" is the group name.
So if you are looking for bugs reported by any user being in the
"editbugs" group, then you can type "%group.editbugs%".
</para>
</section>
<section id="negation">
<title>Negation</title>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment