Menu
▾
▴
[phpBT-dev] CVS: phpbt/docs/sgml bugdetail.sgml,1.1,1.2 bugsearch.sgml,1.2,1.3 primer.sgml,1.6,1.7
|
From: Benjamin C. <bc...@us...> - 2002-04-08 16:39:46
|
Update of /cvsroot/phpbt/phpbt/docs/sgml In directory usw-pr-cvs1:/tmp/cvs-serv5694/sgml Modified Files: bugdetail.sgml bugsearch.sgml primer.sgml Log Message: Updated for 0.8.0 Index: bugdetail.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/bugdetail.sgml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- bugdetail.sgml 17 Oct 2001 13:44:10 -0000 1.1 +++ bugdetail.sgml 8 Apr 2002 15:05:11 -0000 1.2 @@ -8,9 +8,6 @@ <screeninfo>Bug Detail</screeninfo> <mediaobject> <imageobject> -<imagedata fileref="images/shots/user/bugdetail.png" format="PNG"> -</imageobject> -<imageobject> <imagedata fileref="images/shots/user/bugdetail.jpg" format="JPG"> </imageobject> <imageobject> @@ -26,9 +23,9 @@ </screenshot> <para>When changes are made to a bug, an email is sent to the person who reported it and to the person to whom the bug is assigned. However, email is not sent to the person who is making the changes to the bug. So, if a bug has been submitted and assigned to a developer, and then the developer adds comments to the bug, then those comments will be emailed to the reporter but not to the developer. Additional people can be added to receive these change emails by adding them to the CC list. To remove people from the CC list, simply select the people to be removed and submit the form.</para> - +<!-- <para>The set of radio buttons beneath the <guilabel>Update Bug Status</guilabel> label changes depending on the status of the bug. The bug in the screen shot is one that has been newly submitted, so it is unassigned at the moment. If a developer looking at this bug wanted to take ownership, she would click <guilabel>Accept bug</guilabel> and then submit the form. If a bug is resolved as a duplicate of another bug (e.g, bug #77), it will be closed and a comment will be added to this bug and to bug #77 noting that this bug is a duplicate of that one. If there is a developer assigned to be the owner of this component (in this case, "name test"), then the bug can be assigned to that individual by clicking the last radio button.</para> - +--> <para>Files can be added to a bug as attachments by clicking on the <guilabel role="hyperlink">Create Attachment</guilabel> link. This will bring up another form where you can supply a short description and browse for the file to be uploaded. Attachments can be viewed (and can be deleted by administrators) from the attachment list.</para> <para>Adding comments to a bug allows you to provide more detail about what caused the bug or what the expected behavior was, but also allow the developer and the user to communicate about a bug while keeping a history of those notes. Comments that are added to a bug will be emailed as described previously. HTML tags will be stripped from the comments, but there are two special character sequences that can be used to create links when the comments are displayed:</para> Index: bugsearch.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/bugsearch.sgml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- bugsearch.sgml 26 Mar 2002 17:27:59 -0000 1.2 +++ bugsearch.sgml 8 Apr 2002 15:05:11 -0000 1.3 @@ -2,14 +2,11 @@ <sect1 id="bugsearch"> <title>Searching the Bug Database</title> -<para>The query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</para> +<para>There are two versions of the bug query page. The default version is the simple form, which allows you to restrict your search by project and bug status. The advanced query page presents a wide array of options for finding a specific set of bugs, and thus can be a little overwhelming at first sight. By submitting the default form, without selecting any options, a list of all the bugs in the database will be returned. Every option selected will filter out more bugs as you get more specific in your search.</para> <screenshot> <screeninfo>Bug Search</screeninfo> <mediaobject> -<imageobject> -<imagedata fileref="images/shots/user/query.png" format="PNG"> -</imageobject> <imageobject> <imagedata fileref="images/shots/user/query.jpg" format="JPG"> </imageobject> Index: primer.sgml =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/sgml/primer.sgml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- primer.sgml 17 Oct 2001 04:02:28 -0000 1.6 +++ primer.sgml 8 Apr 2002 15:05:11 -0000 1.7 @@ -5,22 +5,19 @@ <sect2 id="createaccount"> <title>Creating an account</title> -<para>You can create a new account by following the link labeled <emphasis role="bold">Open a new account</emphasis>. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</para> +<para>You can create a new account by following the link labeled <emphasis role="bold">Create a new account</emphasis>. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</para> </sect2> <sect2 id="enterbug"> <title>Entering a bug</title> -<para>Once you have logged in to the system you can follow the <emphasis role="bold">Enter Bug</emphasis> link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</para> +<para>Once you have logged in to the system you can follow the <emphasis role="bold">Add a New Bug</emphasis> link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</para> <screenshot> <screeninfo>Project selection</screeninfo> <mediaobject> <imageobject> -<imagedata fileref="images/shots/user/enterbug-chooseproject.png" format="PNG"> -</imageobject> -<imageobject> <imagedata fileref="images/shots/user/enterbug-chooseproject.jpg" format="JPG"> </imageobject> <imageobject> @@ -40,9 +37,6 @@ <screenshot> <screeninfo>Adding a bug</screeninfo> <mediaobject> -<imageobject> -<imagedata fileref="images/shots/user/enterbug-detail.png" format="PNG"> -</imageobject> <imageobject> <imagedata fileref="images/shots/user/enterbug-detail.jpg" format="JPG"> </imageobject> |
