Line Item Input Form

<BODY> <!DOCTYPE HTML PUBLIC "-//SoftQuad Software//DTD HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//EN" "hmpro6.dtd"> <HTML> <HEAD> <TITLE> </TITLE><LINK REL="STYLESHEET" HREF="../adastrastyle.css"> <BASE TARGET="_top"> </HEAD> <BODY VLINK="#FF0000" BGCOLOR="#000000"> <H1>Line Item Report Form </H1> <P>Ad Astra Games uses the <A HREF="http://www.adastragames.com/bugzilla/">Bugzilla</A> engine from Mozilla software to drive its problem reporting database. http://www.adastragames.com/bugzilla/ </P> <P>All you need to create a login ID is provide a valid e-mail address. The system will mail you a password that you can use to log in, and will remember that password in a cookie for you.</P> <P> Before reporting a bug, you should first run a query to see if that bug has already been entered. Click either "Query existing bug reports" on the main screen or "Query" from the footer bar. (The footer is visible on nearly every page in Bugzilla.) </P> <P>The query screen can be a bit intimidating until you're familiar with it; fortunately you can ignore pretty much all of it for now. The first line on the form shows "Summary:" then gives an option list that defaults to "contains all of the words/strings" and then a box for you to enter text. Enter the specific rule you wish to report a problem with (including brackets - (B2.31) or (F1.0) will get the right results, B2.31 or F1.0 may not), and hit search. </P> <P>You will see one of two things. Either a list of 1 or more bugs with a one line entry for each, or "Zarro Boogs found". If it gives a list of bugs, you can look at the Summary column to get a quick idea if your problem is already reported. If you need more information, clicking on the ID of any bug will bring you into the details screen. Scroll down to the bottom of the screen to see the detailed description of the problem. You can return to your list of bugs either with the back button or the "Show list" link. You can also use the First/Last/Prev/Next links to look at other bugs from your query without needing to go back to the list. If it shows "Zarro Boogs found", or the list of bugs doesn't include the problem you wish to report, you can now submit a new bug. </P> <P>Click "Enter new bug" from the main screen or the query listing, or "New" in the footer bar. Select the product you're reporting a problem with, and it will bring you to the Enter Bug screen. There are a lot of selections to make here, but only 4 of them matter. The rest can be left as default; they're either pre-selected for the product, or they're for Ad Astra staff to use when processing bugs.</P> <P> Component: This is the broad category the problem is in. In the case of the AV:Starship Command rulebook, they are the rules sections (A, B, CH, F, etc). The ship book has the different ship classes as the components. Other products will be similarly divided. If a component isn't listed (for example, Right Of Passage in the rulebook), use Miscellaneous as the component. </P> <P>Severity: There are three broad classes of severity: Normal, X-Ref errors and typo. Other values may be used by Ad Astra staff after the bug is submitted, but it's unlikely. </P> <P>X-Ref errors: Anytime there is a reference that goes nowhere, it is an X-Ref error. Examples of X-Ref errors would be references to rules that don't exist (C3.3), diagrams that don't exist or obsolete terminology. Examples of the last would be gyros or capacitors. </P> <P>typo: This is a broad catch-all category for any typographical, grammar, formatting or layout errors. Straight mistyped words, contractions, font type, or diagrams in the wrong place ("example below" actually beside) are all examples of "typo" class problems. </P> <P>normal: Anything that isn't an X-Ref error or a typo falls here. Typically this will be actual problems with mechanics or understanding, although in general if you aren't sure what an error is, leave it at normal severity. </P> <P>Summary: This is a quick description of the problem. To make things as easy as possible for Ad Astra staff, please start the summary with the rules reference, including brackets as in (B3.211). If it isn't in relation to a rule, list the component here (or in the case of miscellaneous problems, the closest approximation. For example "Right of Passage" or "Table of Contents") Description: A detailed description of the problem; be as detailed or concise as is appropriate. Doublecheck what you've put in, and press the "Commit" button. You will see a confirmation screen that shows the bug you've just entered. </P> [an error occurred while processing this directive] <P><I><FONT SIZE="-2">Last Modified on: Wednesday, 14-Nov-2007 16:07:53 MST </FONT></I></P> </BODY> </HTML> </BODY>