head	1.8;
access;
symbols
	TIGRIS_1_1_0RC2:1.6
	TIGRIS_1_1_0RC1:1.6
	TIGRIS_1_1:1.6.0.4
	TIGRIS_1_0_8:1.6
	TIGRIS_1_0_8RC3:1.6
	TIGRIS_1_0_8RC2:1.6
	TIGRIS_1_0_8RC1:1.6
	TIGRIS_1_0_7:1.6
	TIGRIS_1_0_7RC3:1.6
	TIGRIS_1_0_7RC2:1.6
	TIGRIS_1_0_7RC1:1.6
	TIGRIS_1_0_6:1.6
	TIGRIS_1_0_6RC5:1.6
	TIGRIS_1_0_6RC4:1.6
	TIGRIS_1_0_6RC3:1.6
	TIGRIS_1_0_6RC2:1.6
	TIGRIS_1_0_6RC1:1.6
	TIGRIS_1_0_5:1.6
	TIGRIS_1_0_5RC6:1.6
	TIGRIS_1_0_5RC5:1.6
	TIGRIS_1_0_5RC4:1.6
	TIGRIS_1_0_5RC3:1.6
	TIGRIS_1_0_5RC2:1.6
	TIGRIS_1_0_5RC1:1.6
	TIGRIS_1_0_4:1.6
	TIGRIS_1_0_3:1.6
	TIGRIS_1_0_2:1.6
	TIGRIS_1_0_1:1.6
	TIGRIS_1_0:1.6.0.6
	TIGRIS_1_0_0:1.6
	TIGRIS_1_0_0_RC1:1.6.0.2
	dlr:1.1.1
	TIGRIS_0_9_2_4:1.1
	TIGRIS_0_9_2_3:1.1
	HELM_PEER_PORT_BRANCH:1.1.1.1
	TURBINE_PEER:1.1
	TIGRIS_0_9_2_1:1.1
	TIGRIS_0_9_2:1.1.0.6
	TIGRIS_0_8_4:1.1.0.4
	TIGRIS_0_9_0:1.1.0.2;
locks; strict;
comment	@# @;


1.8
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.7;

1.7
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.6;

1.6
date	2001.03.17.00.20.52;	author lori;	state Exp;
branches;
next	1.5;

1.5
date	2001.03.16.00.52.35;	author csjank;	state Exp;
branches;
next	1.4;

1.4
date	2001.03.16.00.50.04;	author csjank;	state dead;
branches;
next	1.3;

1.3
date	2001.03.15.19.50.39;	author csjank;	state Exp;
branches;
next	1.2;

1.2
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.1;

1.1
date	2000.12.30.23.22.01;	author jrobbins;	state Exp;
branches
	1.1.1.1
	1.1.4.1
	1.1.8.1;
next	;

1.1.1.1
date	2001.02.21.00.32.02;	author dlr;	state Exp;
branches;
next	;

1.1.4.1
date	2001.01.16.00.17.44;	author susank;	state Exp;
branches;
next	;

1.1.8.1
date	2001.02.17.18.39.16;	author edk;	state Exp;
branches;
next	;


desc
@@


1.8
log
@html usage revision
@
text
@  <div class="docs" id="booleanchart">
   <h2>Using the Boolean chart</h2>

   <p>The Issuezilla query page allows you to define your search parameters by all fields in the Issue database. To limit your search to a specific set of values in those fields, you can use the "Boolean chart" at the bottom of the page.</p>

   <p>Each Boolean chart can contain one or more <i>terms</i> - the fields/values to search by and how each should be treated - and Boolean operators - either <i>AND</i> or <i>OR</i>.</p>

   <p>To define a term, select an item from each pulldown box, specifying the field and the type of match, and enter a value in the data field. For example, if you select <b>Issue #</b> from the first pulldown, <b>equal to</b> from the second pulldown, and enter 001 in the data field, you will see only issue #001 in your search results.</p>

   <p>The Boolean operators, i.e. the <b>And</b> button and the <b>Or</b> button, allow you to search by multiple terms.</p>

   <p>Clicking the <b>And</b> button allows you to define a new term and have the result of the query include anything that matches <i>both</i> of the terms.</p>

   <p>Clicking the <b>Or</b> button allows you to define a new term and the result of the query will be anything that matches <i>either</i> of the terms.</p>

   <p>You can add as many terms as you like by clicking the <b>And</b> or <b>Or</b> button after each term. You can also use both <b>And</b> and <b>Or</b> in a single query. Terms separated by <b>Or</b> are treated as a single statement. Terms separated by <b>And</b> are treated as separate statements. For example, you could search for all <i>P1</i> and <i>P2</i> issues with a status <i>New</i> or <i>Pending</i>. Your Boolean chart would look like this:</p>

   <p>Status Equal to New <em>OR</em> Status Equal to Pending</p>

   <p><em>AND</em></p>

   <p>Priority Equal to P2 <em>OR</em> Priority Equal to P1</p>

   <p>You can use the <b>Add another Boolean chart</b> button to search for multiple instances of a field that can have several entries associated with a single issue. For example all of the <i>changed</i>... match types and fields like <b>IssuesThisDependsOn</b>, <b>Comments</b>, and <b>CC,</b> etc. can have several entries in a single issue. If you have multiple terms in your search that refer to one field, they will always return the same instance unless the terms appear on different charts.</p>

   <p>For example, if you search for "Priority <i>changed to</i> P5 <b>And</b> Priority <i>changed by</i> person@@addr," your results would include only issues where the person@@addr changed the Priority to P5. However, if you want to find all issues for which person@@addr changed the priority, and for which the priority was changed to P5 by anyone, you would put the two terms in two different charts that would look like this:</p>

   <p>Priority Changed by person@@addr</p>

   <p>Priority Changed to P5</p>

   <div class="courtesylinks">
    <p><a href="ProjectIssues.html">Back to Project Issues help</a><br />
     <a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.7
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@a0 8
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Issuezila Boolean Charts</title>
 </head>

 <body>
d18 1
a18 17
   <table width="100%" border="0" cellpadding="2" cellspacing="0">
    <tr>
     <td>Status</td>

     <td>Equal to</td>

     <td>New</td>

     <td><i>OR</i></td>

     <td>Status</td>

     <td>Equal to</td>

     <td>Pending</td>
    </tr>
   </table>
d22 1
a22 17
   <table width="100%" border="0" cellpadding="2" cellspacing="0">
    <tr>
     <td>Priority</td>

     <td>Equal to</td>

     <td>P2</td>

     <td><i>OR</i></td>

     <td>Priority</td>

     <td>Equal to</td>

     <td>P1</td>
    </tr>
   </table>
d28 3
a30 20
   <table width="100%" border="2" cellpadding="2" cellspacing="0">
    <tr>
     <td>Priority</td>

     <td>Changed by</td>

     <td>person@@addr</td>
    </tr>
   </table>
   

   <table width="100%" border="2" cellpadding="2" cellspacing="0">
    <tr>
     <td>Priority</td>

     <td>Changed to</td>

     <td>P5</td>
    </tr>
   </table>
d33 2
a34 2
    <a href="ProjectIssues.html">Back to Project Issues help</a><br />
     <a href="/servlets/HelpTOC">Back to main Help index</a>
d37 1
a37 2
 </body>
</html>
@


1.6
log
@added help nav links at bottom of doc
@
text
@d1 2
d4 3
a6 51
<head>
<title>Issuezila Boolean Charts</title>
</head>
<body>
<p><span class="Header" nowrap>Using the Boolean chart</span></p>
<span class="PlainText">
<p>The Issuezilla query page allows you to define your search parameters by all fields in the Issue database. To limit your search to a specific set of values in those fields, you can use the "Boolean chart" at the bottom of the page.</p>
<p>Each Boolean chart can contain one or more <i>terms</i> - the fields/values to search by and how each should be treated - and Boolean operators - either <i>AND</i> or <i>OR</i>.</p> 
<p>To define a term, select an item from each pulldown box, specifying the field and the type of match, and enter a value in the data field. For example, if you select <b>Issue #</b> from the first pulldown, <b>equal to</b> from the second pulldown, and enter 001 in the data field, you will see only issue #001 in your search results.</p>
<p>The Boolean operators, i.e. the <b> And</b> button and the <b>Or</b> button, allow you to search by multiple terms.</p>
<p>Clicking the <b>And</b> button allows you to define a new term and have the result of the query include anything that matches <i>both</i> of the terms.</p>
<p>Clicking the <b>Or</b> button allows you to define a new term and the result of the query will be anything that matches <i>either</i> of the terms. </p>
<p>You can add as many terms as you like by clicking the <b>And</b> or <b>Or</b> button after each term. You can also use both <b>And</b> and <b>Or</b> in a single query. Terms separated by <b>Or</b> are treated as a single statement. Terms separated by <b>And</b> are treated as separate statements. For example, you could search for all <i>P1</i> and <i>P2</i> issues with a status <i>New</i> or <i>Pending</i>. Your Boolean chart would look like this:</p>
<table width="710" border="1" cellpadding="0" cellspacing="0">
<tr>
<td width="95"><span class="PlainText">Status</span></td>
<td width="150"><span class="PlainText">Equal to</span></td>
<td width="100"><span class="PlainText">New</span></td>
<td width="45"><span class="PlainText"><i>OR</i></span></td>
<td width="110"><span class="PlainText">Status</span></td>
<td width="100"><span class="PlainText">Equal to</span></td>
<td width="75"><span class="PlainText">Pending</span></td></tr></table>
<i>AND</i>
<table width="710" border="1" cellpadding="0" cellspacing="0">
<tr>
<td width="95"><span class="PlainText">Priority</span></td>
<td width="150"><span class="PlainText">Equal to</span></td>
<td width="100"><span class="PlainText">P2</span></td>
<td width="45"><span class="PlainText"><i>OR</i></span></td>
<td width="110"><span class="PlainText">Priority</span></td>
<td width="100"><span class="PlainText">Equal to</span></td>
<td width="75"><span class="PlainText">P1</span></td>
</tr>
</table>
<p>You can use the <b>Add another Boolean chart</b> button to search for multiple instances of a field that can have several entries associated with a single issue. For example all of the <i>changed</i>... match types and fields like <b>IssuesThisDependsOn</b>, <b>Comments</b>, and <b>CC, </b>etc. can have several entries in a single issue. If you have multiple terms in your search that refer to one field, they will always return the same instance unless the terms appear on different charts. </p>
<p> For example, if you search for &quot;Priority <i>changed to</i> P5 <b>And</b> Priority <i>changed by</i> person@@addr,&quot; your results would include only issues where the person@@addr changed the Priority to P5. However, if you want to find all issues for which person@@addr changed the priority, and for which the priority was changed to P5 by anyone, you would put the two terms in two different charts that would look like this:</p>
<table width="450" border="1" cellpadding="0" cellspacing="0">
<tr>
<td width="120"><span class="PlainText">Priority</span></td>
<td width="145"><span class="PlainText">Changed by</span></td>
<td width="175"><span class="PlainText">person@@addr</span></td>
</tr></table><hr><table width="450" border="1" cellpadding="0" cellspacing="0"><tr>
<td width="120"><span class="PlainText">Priority</span></td>
<td width="145"><span class="PlainText">Changed to</span></td>
<td width="175"><span class="PlainText">P5</span></td>
</tr>
</table>

<hr noshade size=1>
<a href="ProjectIssues.html">Back to Project Issues help</a><br>
<a href="/servlets/HelpTOC">Back to main Help index</a>
d8 87
a94 2
</span>
</body>
d96 2
@


1.5
log
@added span class tag to tables
@
text
@d49 5
d56 1
a56 1
</html>@


1.4
log
@added span class tag to tables
@
text
@d1 51
a51 84
<html>
<head>
<title>Issuezila Boolean Charts</title>
</head>
<body>
<p><span class="Header" nowrap>Using the Boolean chart</span></p>

<span class="PlainText">
<p> The Issuezilla query page allows you to define your search parameters by all 
  fields in the Issue database. To limit your search to a specific set of values 
  in those fields, you can use the "Boolean chart" at the bottom of the page. 
<p> Each Boolean chart can contain one or more <i>terms</i> - the fields/values 
  to search by and how each should be treated - and Boolean operators - either 
  <i>AND</i> or <i>OR</i>. 
<p>To define a term, select an item from each pulldown box, specifying the field 
  and the type of match, and enter a value in the data field. For example, if 
  you select <b>Issue #</b> from the first pulldown, <b>equal to</b> from the 
  second pulldown, and enter 001 in the data field, you will see only issue #001 
  in your search results. 
<p>The Boolean operators, i.e. the <b> And</b> button and the <b>Or</b> button, 
  allow you to search by multiple terms. 
<p>Clicking the <b>And</b> button allows you to define a new term and have the 
  result of the query include anything that matches <i>both</i> of the terms. 
<p> Clicking the <b>Or</b> button allows you to define a new term and the result 
  of the query will be anything that matches <i>either</i> of the terms. 
<p> You can add as many terms as you like by clicking the <b>And</b> or <b>Or</b> 
  button after each term. You can also use both <b>And</b> and <b>Or</b> in a 
  single query. Terms separated by <b>Or</b> are treated as a single statement. 
  Terms separated by <b>And</b> are treated as separate statements. For example, 
  you could search for all <i>P1</i> and <i>P2</i> issues with a status <i>New</i> 
  or <i>Pending</i>. Your Boolean chart would look like this:</p>
<table width="710" border="1" cellpadding="0" cellspacing="0">
  <tr> 
    <td width="95">Status</td>
    <td width="150">Equal to</td>
    <td width="100">New</td>
    <td width="45"><i>OR</i></td>
    <td width="110">Status</td>
    <td width="100">Equal to</td>
    <td width="75">Pending</td>
  </tr></table>
<i>AND</i> 
<table width="710" border="1" cellpadding="0" cellspacing="0">
  <tr> 
    <td width="95">Priority</td>
    <td width="150">Equal to</td> 
	<td width="100">P2</td>
    <td width="45"><i>OR</i></td>
    <td width="110">Priority</td>
    <td width="100">Equal to</td>
    <td width="75">P1</td>
  </tr>
</table>

<p>You can use the <b>Add another Boolean chart</b> button to search for multiple 
  instances of a field that can have several entries associated with a single 
  issue. For example all of the <i>changed</i>... match types and fields like 
  <b>IssuesThisDependsOn</b>, <b>Comments</b>, and <b>CC, </b>etc. can have several 
  entries in a single issue. If you have multiple terms in your search that refer 
  to one field, they will always return the same instance unless the terms appear 
  on different charts. </p>
<p> For example, if you search for &quot;Priority <i>changed to</i> P5 <b>And</b> 
  Priority <i>changed by</i> person@@addr,&quot; your results would include only 
  issues where the person@@addr changed the Priority to P5. However, if you want 
  to find all issues for which person@@addr changed the priority, and for which 
  the priority was changed to P5 by anyone, you would put the two terms in two 
  different charts that would look like this:</p>
<table width="450" border="1" cellpadding="0" cellspacing="0">
  <tr> 
    <td width="120">Priority</td>
    <td width="145">Changed by</td>
    <td width="175">person@@addr</td>
  </tr></table>    
<hr> 
<table width="450" border="1" cellpadding="0" cellspacing="0">
  <tr> 
    <td width="120">Priority</td>
    <td width="145">Changed to</td>
    <td width="175">P5</td>
  </tr>
</table>
</span>
</body>
</html>
@


1.3
log
@Completely rewrote this to be clear and give usable information.
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@@


1.2
log
@added <title> tags to all files
@
text
@d1 84
a84 75
<HTML>
<HEAD>

<TITLE>Issuezila Boolean Charts</TITLE>

</HEAD>
<BODY>
<!-- style/format note: Headings/fonts should be updated to conform to scast style -->

<H2>The "boolean chart" section of the query page</H2>

<P>
The Issuezilla query page is designed to be reasonably easy to
use. But, with such ease of use always comes some lack of power.  The
"boolean chart" section is designed to let you do very powerful
queries, but it's not the easiest thing to learn (or explain).

<p>
So.

<p>
The boolean chart starts with a single "term".  A term is a
combination of two pulldown menus and a text field. You choose items
from the menus, specifying "what kind of thing am I searching for" and
"what kind of matching do I want", and type in a value on the text
field, specifying "what should it match".

<p>
The real fun starts when you click on the "Or" or "And" buttons.  If
you bonk on the "Or" button, then you get a second term to the right
of the first one.  You can then configure that term, and the result of
the query will be anything that matches either of the terms.

<p>
Or, you can bonk the "And" button, and get a new term below the
original one, and now the result of the query will be anything that
matches both of the terms.

<p>
And you can keep clicking "And" and "Or", and get a page with tons of
terms.  "Or" has higher precedence than "And".  (In other words, you
can think of each line of "Or" stuff as having parenthesis around it.)

<p>
The most subtle thing is this "Add another boolean chart" button. This
is almost the same thing as the "And" button.  The difference is if
you use one of the fields where several items can be associated with a
single issue.  This includes "Comments", "CC", and all the "changed
[something]" entries.  Now, if you have multiple terms that all talk
about one of these fields, it's ambiguous whether they are allowed to
be talking about different instances of that field.  So, to let you
have it both ways, they always mean the same instance, unless the
terms appear on different charts.

<p>
For example: if you search for "priority changed to P5" and "priority
changed by person@@addr", it will only find issues where the given
person at some time changed the priority to P5.  However, if what you
really want is to find all issues where the milestone was changed at
some time by the person, and someone (possibly someone else) at some
time changed the milestone to P5, then you would put the two terms in
two different charts.

<p>
Clear as mud?  Please, I beg you, rewrite this document to make
everything crystal clear, and send the improved version to <a
href="mailto:tara@@tequilarista.org">Tara</a>. ("Boolean chart" is a
terrible term; anyone got a better one I can use instead?)


<P><FONT SIZE="-1">Last modified: Sat Sep 23 10:52:57 PDT 2000</FONT>


</BODY>
</HTML>
@


1.1
log
@moved core documentation into helm, fewer overrides need to be in instances now
@
text
@d1 7
d74 2
@


1.1.1.1
log
@Replacing the HEAD with the HELM_PEER_PORT_BRANCH.
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>Issuezila Boolean Charts</TITLE>

</HEAD>
<BODY>
a66 2
</BODY>
</HTML>
@


1.1.8.1
log
@porting changes from the head to the branch
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>Issuezila Boolean Charts</TITLE>

</HEAD>
<BODY>
a66 2
</BODY>
</HTML>
@


1.1.4.1
log
@adding the generic, default docs into this branch, bc they are in the head and nec for instantiations using stable branches
@
text
@@

