1107315 - Update Boolean Charts documentation to match new UI

Status: RESOLVED FIXED

(Bugzilla :: Documentation, defect)

Description

[Gervase Markham [:gerv]]

http://bugzilla.readthedocs.org/en/latest/using/finding.html section 2.5.4.1 documents the Boolean Charts, but we've updated it to a new API (perhaps bug 647649?). We need to update the docs to match.

Gerv

Comment 1

[Gervase Markham [:gerv]]

Attachment: Patch v.1

Mark, care to take a look at this one?

Gerv

Comment 2

[Mark Côté [:mcote]]

Comment on attachment 8542165 [details] [diff] [review]
Patch v.1

Review of attachment 8542165 [details] [diff] [review]:
-----------------------------------------------------------------

Great!  Some nits below.

::: docs/en/rst/using/finding.rst
@@ +96,5 @@
> +:guilabel:`Time Since Assignee Touched` and other things it may be useful to
> +search on.
> +
> +There are a wide range of *operators* available, not all of which may make
> +sense for a particular field. There are various string matching operations

string-matching operations

@@ +98,5 @@
> +
> +There are a wide range of *operators* available, not all of which may make
> +sense for a particular field. There are various string matching operations
> +(including regular expressions), numerical comparisons (which also work for
> +dates), and also the ability to search for change information - when a field

Replace hyphen with colon or proper em dash.

@@ +102,5 @@
> +dates), and also the ability to search for change information - when a field
> +changed, what it changed from or to, and who did it. There are special
> +operators for :guilabel:`is empty` and :guilabel:`is not empty`, because
> +Bugzilla can't tell the difference between a value field left blank on
> +purpose, and one left blank by accident.

No comma.

@@ +105,5 @@
> +Bugzilla can't tell the difference between a value field left blank on
> +purpose, and one left blank by accident.
> +
> +You can have an arbitrary number of rows, and the dropdown box above them
> +defines how they relate - :guilabel:`Match ALL of the following separately`,

Replace hyphen with colon or proper em dash.

@@ +106,5 @@
> +purpose, and one left blank by accident.
> +
> +You can have an arbitrary number of rows, and the dropdown box above them
> +defines how they relate - :guilabel:`Match ALL of the following separately`,
> +:guilabel:`Match ANY of the following separately`, and :guilabel:`Match ALL of

s/and/or/?

@@ +124,5 @@
> +Advanced Features
> +-----------------
> +
> +If you click :guilabel:`Show Advanced Features`, then more capabilities appear.
> +You can negate any row with a checkbox (see below), and also group lines of the

Remove comma.

@@ +182,2 @@
>  user running the query or the user to whom each bug is assigned). For
>  example, you may want to find all bugs which are assigned to the person

I know you didn't edit this line, but the "which" should be "that", if you want to fix that. :)

@@ +190,5 @@
>  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.
>  
> +This feature also let you search by a user's group memberships. If the

lets

Comment 3

[Gervase Markham [:gerv]]

Attachment: Patch v.2

Review comments addressed; carrying over mcote r+.

Gerv

Comment 4

[Gervase Markham [:gerv]]

To ssh://[e-mail]/bugzilla/bugzilla.git
   c396517..43241d1  master -> master

To ssh://[e-mail]/bugzilla/bugzilla.git
   4e15a13..c97950a  5.0 -> 5.0

Gerv