[phpBT-dev] CVS: phpbt/docs/html adminguide.html,1.4,1.5 configuration.html,1.3,1.4 devguide.html,1.5,1.6 devstandards.html,1.6,1.7 userguide.html,1.3,1.4

[Benjamin C. <bc...@us...>]

Update of /cvsroot/phpbt/phpbt/docs/html
In directory usw-pr-cvs1:/tmp/cvs-serv15278/html

Modified Files:
	adminguide.html configuration.html devguide.html 
	devstandards.html userguide.html 
Log Message:
User primer done

Index: adminguide.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- adminguide.html	2001/10/03 04:03:55	1.4
+++ adminguide.html	2001/10/03 13:38:06	1.5
@@ -99,7 +99,7 @@
 ><DIV
 CLASS="ABSTRACT"
 ><A
-NAME="AEN32"
+NAME="AEN48"
 ></A
 ><P
 >One of the main design goals of phpBugTracker is to make installation and administration easy.  In fact, the difficulty of installing bugzilla was a key motivator for phpBugTracker's existence.</P

Index: configuration.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/html/configuration.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- configuration.html	2001/10/03 04:03:55	1.3
+++ configuration.html	2001/10/03 13:38:06	1.4
@@ -84,7 +84,7 @@
 ><DIV
 CLASS="ABSTRACT"
 ><A
-NAME="AEN84"
+NAME="AEN100"
 ></A
 ><P
 >The options listed in this section can be configured by the <TT

Index: devguide.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- devguide.html	2001/10/03 04:03:55	1.5
+++ devguide.html	2001/10/03 13:38:06	1.6
@@ -113,7 +113,7 @@
 ><DIV
 CLASS="ABSTRACT"
 ><A
-NAME="AEN189"
+NAME="AEN205"
 ></A
 ><P
 >Adding on to or extending phpBugTracker should be easy for those with a knowledge of PHP and SQL.  New developers are always welcome to join the project at <A
@@ -136,7 +136,7 @@
 ><DIV
 CLASS="ABSTRACT"
 ><A
-NAME="AEN194"
+NAME="AEN210"
 ></A
 ><P
 >phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph.  Of course a web server and a database are also necessary.</P
@@ -161,7 +161,7 @@
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN200"
+NAME="AEN216"
 >3.1.1.1. Database Abstraction</A
 ></H3
 ><P
@@ -220,7 +220,7 @@
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN212"
+NAME="AEN228"
 >3.1.1.2. Templates</A
 ></H3
 ><P

Index: devstandards.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/html/devstandards.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- devstandards.html	2001/10/03 04:03:55	1.6
+++ devstandards.html	2001/10/03 13:38:06	1.7
@@ -77,7 +77,7 @@
 ><DIV
 CLASS="ABSTRACT"
 ><A
-NAME="AEN218"
+NAME="AEN234"
 ></A
 ><P
 >			This section details the coding and process standards to be 

Index: userguide.html
===================================================================
RCS file: /cvsroot/phpbt/phpbt/docs/html/userguide.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- userguide.html	2001/10/03 04:03:55	1.3
+++ userguide.html	2001/10/03 13:38:06	1.4
@@ -99,7 +99,7 @@
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN12"
+NAME="CREATEACCOUNT"
 >1.1.1. Creating an account</A
 ></H2
 ><P
@@ -137,7 +137,54 @@
 ></P
 ></DIV
 ><P
->..</P
+>Once you have chosen a project, or if there is only one project in the system, you will see the bug entry page.  The <SPAN
+CLASS="bold"
+><B
+CLASS="EMPHASIS"
+>Version</B
+></SPAN
+> and <SPAN
+CLASS="bold"
+><B
+CLASS="EMPHASIS"
+>Component</B
+></SPAN
+> fields allow you to specify details about which part or version of the product that produces this bug.  The <SPAN
+CLASS="bold"
+><B
+CLASS="EMPHASIS"
+>Summary</B
+></SPAN
+> field should be a short but specific summary of the problem, while the <SPAN
+CLASS="bold"
+><B
+CLASS="EMPHASIS"
+>Description</B
+></SPAN
+> field should include details about the behavior observed, how that behavior differs from expected behavior, and the steps to reproduce the problem.  If the product being tested is web-based, you can use the <SPAN
+CLASS="bold"
+><B
+CLASS="EMPHASIS"
+>URL</B
+></SPAN
+> field to provide a link directly to the problem.  The <SPAN
+CLASS="bold"
+><B
+CLASS="EMPHASIS"
+>Add another</B
+></SPAN
+> checkbox, if checked, will present another bug entry form when you submit a bug, instead of taking you to the bug list.</P
+><DIV
+CLASS="MEDIAOBJECT"
+><P
+><IMG
+SRC="images/shots/user/enterbug-detail.png"
+ALT="Screen shot of entering a bug report."
+></IMG
+></P
+></DIV
+><P
+>That's it!  The bug has been entered, and it's ready to be reviewed and fixed by the developers.</P
 ></DIV
 ></DIV
 ></DIV