188'body'=>'The bug ID is a unique identification number that can be used to to quickly locate it. The ID is also used for duplicates and dependencies. Marking a bug as "hidden" will prevent all users who cannot see hidden bugs (see the BugStrike manual regarding permissions). Hiding is useful for critical security issues that you do not want to be made public.'
198'body'=>'The reporter is the user who is responsible for the initial bug report. If you need to get follow-up information, you should ask this user.'
208'body'=>'The product, component, and version show the general area where the problem occurs. Products are broad--for instance a car--whereas components would be like a door, using our car analogy. Versions show the specific revision at which the problem occurs.'
223'body'=>'The resolution is the explanation for the status. Usually the resolution is set when a bug is marked "Closed" in the status field.'
228'body'=>'Severity is the degree of the problem. This allows differentiation between a critical security flaw versus a slight annoyance with a work-around.'
233'body'=>'The priority shows the degree of celerity with which the bug will be fixed. This is different from severity in that, a bug could be a valid issue, but it could be for an old version and thus the priority wouldn\'t be high.'
243'body'=>'If a bug is affected by another bug, you can enter the ID of the bug that affects this bug here. You can enter multiple values into this field by separating the IDs with spaces.'
250The "Automation" drop-down next to this box (which may be hidden) will allow you to perform a common task. These administrator-defined tasks can change any of the bug fields automatically and then add an automatic reply. If you change a field that will be altered by the action, the action\'s change will take precedence. Also, if you enter a comment and the action specifies a comment, the automatic comment will be attached to yours.'