locale/en_US/manual-xml/admin.xml

   1 <chapter id="admin" revision="$Revision$">
   2         <title>The Administration Panel</title>
   3
   4         <!-- =================================================================== -->
   5
   6         <section id="admin.about">
   7                 <title>About the Administration Panel</title>
   8                 <para>Once you have logged into your user account, you will see an "Administration" tab in the top navigation bar. Click this to be presented with the login screen. Here, login again for an added layer of security.</para>
   9
  10                 <para>In the administration panel, there are numerous options and features that can be accessed through the <link linkend="admin.menu">main menu</link>.</para>
  11
  12                 <para>If you would like more information about a feature, most sections have a small <strong>Help</strong> link in the upper-right corner. You can click this or the section's title to bring up the documentation page for the specific section.</para>
  13         </section>
  14
  15         <!-- =================================================================== -->
  16
  17         <section id="admin.menu">
  18                 <title>The Main Menu</title>
  19                 <para>The primary page of the administration screen is the main menu:</para>
  20
  21                 <mediaobject>
  22                         <imageobject>
  23                                 <imagedata fileref="images/admin_index/main_menu.png" format="PNG" align="center" />
  24                         </imageobject>
  25                 </mediaobject>
  26
  27                 <para>In this menu there is a listing of all the various mutable aspects of your &product; installation. In this manual, we will explain each item in the main menu in the order that they appear.</para>
  28
  29                 <para>We should also note that any option available in the main menu is also in the navigation menu (the pull down bar in the upper-left corner of the window):</para>
  30
  31                 <mediaobject>
  32                         <imageobject>
  33                                 <imagedata fileref="images/admin_index/navigation_menu.png" format="PNG" align="center" />
  34                         </imageobject>
  35                 </mediaobject>
  36
  37                 <para>The <em>Administration Location</em> section of the navigation is simple: the <em>Home</em> link returns you to the main menu and the <em>Logout</em> link logs you out of the administration panel.</para>
  38
  39                 <note>The logout link in the administration panel will not log you out of the entire &product; system--just the administration panel. However, the opposite is true of the logout link in the non-administration interface: if you log out there, you will also be logged out of the administration panel.</note>
  40         </section>
  41
  42         <!-- =================================================================== -->
  43
  44         <section id="admin.settings">
  45                 <title>Bugdar Settings</title>
  46                 <para>Bugdar's main options are broken up into three different sections: <em>General Options</em>, <em>Bug Reporting Options</em>, and <em>Pagination Options</em>. For the most part, you will only have to alter the general settings. In the following three pages, we will explain the key options of each page.</para>
  47
  48                 <!-- ################################################################### -->
  49
  50                 <section id="admin.settings.general">
  51                         <title>General Options</title>
  52                         Most of the general settings are explained by their descriptions, however a few of the options are explicated here.
  53
  54         <strong>Tracker Title</strong>: This is the name of the entire bug tracking system. The value of this setting will appear at the top of the bug tracker and in most emails sent out to users.
  55
  56         <strong>Tracker Base URL</strong>: Set this to the root URL of your tracker--the initial location of the tracker in your web browser. Make sure that there is no trailing slash ("/") at the end of the URL as it could possibly break links that the URL is used in.
  57
  58         <strong>Date Format</strong>: For most users, this option will not need to change as the default is perfectly fine. However, if you wish to change the way in which dates appear in your bug tracker, you will need to use PHP's date formatting characters. Follow the table <link xlink:href="http://www.php.net/date">here</link> for the formatting characters.
  59                 </section>
  60
  61                 <!-- ################################################################### -->
  62
  63                 <section id="admin.settings.reporting">
  64                         <title>Bug Reporting Options</title>
  65                         <strong>Allow HTML in Bug Reports</strong>: This is an option that should be set to <em>No</em> unless there is good reason to change it. By allowing HTML in bug reports, users would be able to post malicious code that could break the display of the tracker and exploit the system via JavaScript. Only enable this option if you are confident in the users of the system, generally only in private bug trackers.
  66
  67         The rest of the options in <em>Bug Reporting Options</em> are defaults. What that means is that in the new report screen, these values will be entered in by default. If a user has permissions to change the field, he or she can; however, if the user does not, this value will be inserted.
  68                 </section>
  69
  70                 <!-- ################################################################### -->
  71
  72                 <section id="admin.settings.pagination">
  73                         <title>Pagination Options</title>
  74                         The pagination options are advanced features. If you are a novice user and do not have to worry about server load with BugStrike, these settings do not need changing.
  75
  76         These settings control the number of bugs that appear in a listing and how many page navigation links are displayed.
  77
  78         <strong>Default Per-Page Amount</strong>: The default number of items to be displayed on a single page.
  79
  80         <strong>Maximum Per-Page Value</strong>: If a user manually enters a per-page amount, it cannot exceed this value; if it does, the system will use this value instead. If server load is a concern for your system, this setting may need to be lowered.
  81
  82         <strong>Number of Page Links</strong>: This controls how many page navigator links appear on either side of the current page. Settings this to <em>0</em> will display all pages, which is highly not recommended. A setting greater than <em>5</em> is also not recommended.
  83                 </section>
  84
  85         </section>
  86
  87         <!-- =================================================================== -->
  88
  89         <section id="admin.language">
  90                 <title>Manage Languages</title>
  91                 In the <em>Manage Languages</em> section, you are presented with the language manager:
  92
  93                 <mediaobject>
  94
  95                         <imageobject>
  96
  97                                 <imagedata fileref="images/language_manage/language_manager.png" format="PNG" align="center" />
  98
  99                         </imageobject>
 100
 101                 </mediaobject>
 102
 103 In Bugdar, localization is a complicated process which is explained in the <a href="page://19" target="_blank">ISSO manual</a>. What you need to know, however, is that the actual English text is embedded in templates and files. When a new language is added, this English text is looked up against a table of the language's translated text; if there's an entry for a given phrase (called a <em>string</em>), it displays that instead.
 104
 105 What this means is that the default language ("English (US)") doesn't need to exist. However, we have left it in place because if an administrator wants to change a string, all he or she has to do is edit a translation and then reload the XML file. All of this will be explained later in the manual.
 106
 107 The language manager has an important link next to each language: <strong>[Reload XML]</strong>. When a language is reloaded, the cache of strings is flushed and recreated from the XML file. This needs to be done if changes made to a language XML file are to be displayed. You will learn about this in the next section.
 108
 109                 <!-- ################################################################### -->
 110
 111                 <section id="admin.language.edit">
 112                         <title>Adding or Editing a Language</title>
 113                         When you add or edit a language, you are presented with this screen:
 114
 115                         <mediaobject>
 116
 117                         <imageobject>
 118
 119                                 <imagedata fileref="images/language_edit/edit_language.png" format="PNG" align="center" />
 120
 121                         </imageobject>
 122
 123                 </mediaobject>
 124
 125         <strong>Title</strong>: The name of the language that is to be displayed to users (if they can select it) and in the administration panel.
 126
 127         <strong>Character Set</strong>: This character set often determines what symbols can be displayed on a page. English can be <em>iso-8859-1</em> or <em>utf-8</em>, either value will work. By default, however, we have set it to be <em>utf-8</em> because it will display most characters. If you are unsure, use <em>utf-8</em>.
 128
 129         <strong>Direction</strong>: This determines the direction of the text on a page. For instance, English is read left-to-right, while Arabic is read right-to-left.
 130
 131         <strong>Path to XML</strong>: This is the most important setting as it is the path to the translated strings. The default strings file is in <em>./includes/strings/english-us.strings.xml</em>. We recommend placing additional string files in the <em>includes/strings/</em> folder for continuity.
 132
 133         Strings are stored in this XML file, however, they can be cached in the database (see the <em>Debug Mode</em> setting here) to increase speed. If you make changes to the XML file and you do not have debug mode enabled, you will need to reload the language. You can reload the language by clicking <strong>[Reload Language]</strong> in the <link linkend="admin.language">language manager</link>.
 134
 135         <strong>User Selectable</strong>: If this enabled, users will be able to select this language in their options. If it is not, then it will be a private language and only viewable in the administration panel.
 136
 137         <strong>Debug Mode</strong>: Debug mode is a special setting that allows strings to be read directly from the XML file on every page load. This is very useful for translators as they can see their results without having to reload the XML every time. If this setting is disabled, which it should be in a production environment, then the strings will be cached from the XML file in the database. This cache will need to be rebuilt (by clicking <strong>[Reload Language]</strong> in the  <link linkend="admin.language">language manager</link>) if any changes made to the XML file are to be displayed.
 138                 </section>
 139
 140                 <!-- ################################################################### -->
 141
 142                 <section id="admin.language.translate">
 143                         <title>Translating a Language</title>
 144                         Translating strings for BugStrike follows the same rules as translating strings for any other ISSO-based application.
 145
 146         This page will give you the information that is BugStrike-specific to translating. However, for the general practice of translating in ISSO, please refer to the <a href="page://22" target="_blank">ISSO translation manual</a>.
 147
 148         The "master strings file" (as it is called in the ISSO translation manual) is located at <em>includes/strings/english-us.strings.xml</em>. When you are translating, you will need to:
 149
 150         a) Duplicate the file, if you are editing the XML strings directly, or
 151         b) Download the XML file to your computer (if you have not already) and then specify that file as the master in the translation tool.
 152
 153         For further instructions, please consult the ISSO manual.
 154                 </section>
 155
 156                 <!-- ################################################################### -->
 157
 158                 <section id="admin.language.upgrade">
 159                         <title>Languages and Upgrades</title>
 160                         When a new version of Bugdar is released, a small strings file will be placed in <em>install/strings/</em>. This smaller file is a localization-delta file (localization changes). You can read more about the format of the file in the <a href="page://24">ISSO manual</a>.
 161
 162         The files in the <em>install/strings/</em> folder are labeled by version number. If you upgraded from 1.0.0 to 1.0.1, you would look for the <em>1-0-1.strings.xml</em> file and then merge it into your strings file.
 163
 164         If you were to upgrade to a version more than one version above, then you will need to use all the string files. For example, if you were running 1.3.2 and you wanted to upgrade to 1.3.5 (and versions 1.3.3 and 1.3.4 existed), you would need to repeat the merging process for <strong>all</strong> those string files.
 165
 166         For information on how to merge--both manually and using the translation tool--see the <a href="page://24">ISSO manual</a>.
 167                 </section>
 168
 169         </section>
 170
 171         <!-- =================================================================== -->
 172
 173         <section id="admin.userhelp">
 174                 <title>Edit User Help</title>
 175                 The user help manager allows you to edit the help text that is displayed in popups in the user's browser. Next to fields that are help-enabled, a small "?" is placed next to the name of the field; clicking this results in a small pop-up that displays help text.
 176
 177 By default, Bugdar has default text entries for all the fields. These entries cannot be deleted (but the text can be modified) as they are standard Bugdar fields.
 178
 179 The help text for custom fields is set through the <link linkend="admin.customfields.options">description field</link> in the custom field editor.
 180
 181 You can also create your own help text entries by clicking <strong>[Add New Help Text]</strong>. You then enter a unique key that is used to identify the text, the title of the text, and then the body.
 182
 183 Once you have created a custom entry, you can place the following code in any Bugdar template to create the help link:
 184
 185 [php]$help[UNIQUE_KEY][/php]
 186
 187 ... where "UNIQUE_KEY" is the unique key you specified.
 188         </section>
 189
 190         <!-- =================================================================== -->
 191
 192         <section id="admin.products">
 193                 <title>Products and Versions</title>
 194                 Bugdar organizes bugs into products and versions. When a user enters a bug report, he or she is required to specify a product <strong>and</strong> a version. Therefore, you need at least one product and one version in your system to be usable.
 195
 196 Components are essentially sub-products. They behave in the exact same fashion as products (in that they require a version to be selected, too) but they are like a part of the project. For instance, in a calendar application there could be components for making events, displaying the calendar, notifications and reminders, etc. These are smaller--but yet still significant--portions of the product.
 197
 198 In the product manager, you see this:
 199
 200                 <mediaobject>
 201
 202                         <imageobject>
 203
 204                                 <imagedata fileref="images/products_and_versions/product_manager.png" format="PNG" align="center" />
 205
 206                         </imageobject>
 207
 208                 </mediaobject>
 209
 210 This screen allows you to change the display order (the lower the value, the higher it appears in the list) and manage any components or versions. If you wish to add a component or version, simply choose the option from the pulldown on the far-right.
 211
 212 In this screen, products (but not components) are bold, both components and products are underlined, and versions have no special formatting. This interface feature will help you differentiate (along with the depth marks) which is a product and which is a version.
 213
 214 [note]A product has all of its versions and then any global versions. A component will inherit the global versions, its product's versions along with the versions defined specifically for the component. This allows you to specify components without locally-defined versions; instead, they can be inherited.[/note]
 215         </section>
 216
 217         <!-- =================================================================== -->
 218
 219         <section id="admin.standardfields">
 220                 <title>Priorities, Resolutions, Severities, and Statuses</title>
 221                 Priorities, resolutions, severities, and statuses all follow the same pattern when adding or editing a new one and therefore they are grouped together in this document.
 222
 223 The following is an explanation of each bug field:
 224
 225 <strong>Priority</strong>: This is the field that represents the celerity with witch developers should work with to resolve the bug.
 226
 227 <strong>Resolution</strong>: Usually this is the reason why a certain bug has been marked "closed." For instance, if a bug is not reproducible, then it would be closed and this field would probably be set to "Works for Me."
 228
 229 <strong>Severity</strong>: The user defines this field based on how critical the bug is. Be careful to not confuse this with priority. An example is if a security issue (marked "Critical" in this field) was found in an old version of the software that did not affect the new version; while the severity may be critical, because the version is old, the priority would not need to be marked "High."
 230
 231 <strong>Status</strong>: The state of the bug; this is usually set when the bug is triaged--marked as "Verified" or "Assigned" and then again when it is "Closed." It is usually changed to mark a major shift in the bug's occurrence in a product and version.
 232
 233 All of these fields have a title, which is the value of the field; for instance "Normal" is the title of a default priority. Each field also has a display order; this value can be used to control the appearance of a given value in the selection list. If you want to change the default value for new bug reports, see <link linkend="admin.settings.reporting">here</link>.
 234
 235 [note]The status field also has a colour field associated with it. By filling this value in with a HEX code (be sure to include the <em>#</em> when you specify the value), the background colour of the bug rows in lists will fill to this colour according to bug status (this is a user option). For instance, any unconfirmed bugs will be highlighted in red when viewing the bug list.[/note]
 236         </section>
 237
 238         <!-- =================================================================== -->
 239
 240         <section id="admin.customfields">
 241                 <title>Custom Bug Fields</title>
 242                 Bugdar offers many fields to help you track and triage bugs. However, sometimes additional fields are needed for your specific setup. The additional bug fields feature allows you to create those extra fields and exert fine control over the fields.
 243
 244 The manager shows you all the information regarding the field:
 245
 246                 <mediaobject>
 247
 248                         <imageobject>
 249
 250                                 <imagedata fileref="images/custom_bug_fields/custom_field_manager.png" format="PNG" align="center" />
 251
 252                         </imageobject>
 253
 254                 </mediaobject>
 255
 256 There are three types of field that can be created: single-line text boxes, check boxes, and drop-down menus. When you click <strong>[Add New Bug Field]</strong>, you are presented with this screen:
 257
 258                 <mediaobject>
 259
 260                         <imageobject>
 261
 262                                 <imagedata fileref="images/custom_bug_fields/add_new_field_type.png" format="PNG" align="center" />
 263
 264                         </imageobject>
 265
 266                 </mediaobject>
 267
 268 Here you select the type of field you want. After selecting the type of field you want and pressing <strong>[Submit]</strong>, you are taken to the options screen; here you specify all the various options for your field. This is discussed <link linkend="admin.customfields.options">here</link>.
 269
 270                 <!-- ################################################################### -->
 271
 272                 <section id="admin.customfields.options">
 273                         <title>Custom Bug Field Options</title>
 274                         All custom fields have the same standard options:
 275
 276                         <mediaobject>
 277
 278                         <imageobject>
 279
 280                                 <imagedata fileref="images/custom_bug_fields_options/global_options.png" format="PNG" align="center" />
 281
 282                         </imageobject>
 283
 284                 </mediaobject>
 285
 286         <strong>Field Type</strong>: The type of field that you are creating (selected previously)
 287
 288         <strong>Description</strong>: Describe the field and its use; this is displayed as the help text to users.
 289
 290         <strong>Required</strong>: Whether or not the field is required to be specified by the user.
 291
 292         <strong>Can Be Searched</strong>: Whether or not the field appears on the search form.
 293
 294         Additionally, each field has custom permissions that you can set on a per-usergroup level (these can also be set in the <link linkend="admin.usergroups">usergroup editor</link>. You can specify <em>No Permission</em>, <em>Can View</em>, or <em>Can View and Edit</em> settings:
 295
 296                         <mediaobject>
 297
 298                         <imageobject>
 299
 300                                 <imagedata fileref="images/custom_bug_fields_options/field_permissions.png" format="PNG" align="center" />
 301
 302                         </imageobject>
 303
 304                 </mediaobject>
 305
 306         Each type of field also has a unique set of options:
 307
 308         <u>Single-Line Text Field</u>
 309         <blockquote>
 310         <strong>Default Value</strong>: Specify a default value for the field to be entered in new reports.
 311
 312         <strong>Regular Expression Match</strong>: You can use a regular expression to match against the field's contents and the value will be rejected if the match fails.
 313
 314         <strong>Maximum Length</strong>: If you want to limit the amount of characters (including spaces) that can be typed in the field, you can specify it here.
 315         </blockquote>
 316         <u>Checkbox Flag</u>
 317         <blockquote>
 318         <strong>Checked By Default</strong>: Setting this to <em>Yes</em> will make the checkbox clicked on.
 319         </blockquote>
 320         <u>Drop-Down Menu</u>
 321         <blockquote>
 322         <strong>Selection Values</strong>: A list of values to display in the menu, separated by a new line. If you remove a value that has been set by some bugs, it will still display in the non-edit mode of the bug display.
 323
 324         <strong>Make the First Option Default</strong>: If you want to make the first option in the selection values list (above) be selected by default, change this to <em>Yes</em>. Otherwise, the menu will have a blank option selected by default.
 325         </blockquote>
 326                 </section>
 327
 328         </section>
 329
 330         <!-- =================================================================== -->
 331
 332         <section id="admin.automations">
 333                 <title>Automations</title>
 334                 Often, the same task is performed repeatedly, such as marking a bug "closed and fixed," or "not reproducible," or "please provide more information."
 335
 336 These common responses often involve changing multiple fields (status, resolution, etc.) and then leaving a standard comment. Automatic actions make this process significantly easier as you simply define a "macro" of sorts that sets all of the fields and enters the comment automatically.
 337
 338 You use these "macros" when viewing a bug. You select one of the automatic actions from a list and when you commit the changes to the bug, the changes specified in the automatic action will be applied.
 339
 340 The three required fields are:
 341
 342 <strong>Name</strong>: The name of the automatic action. This is displayed on the bug display and users select an action by this name.
 343
 344 <strong>Description</strong>: Remarks about what the action does.
 345
 346 <strong>Add Comment</strong>: The comment to add to the bug when the action is run. If the user has specified a comment and runs the automatic action at the same time, the automatic comment will be appended to the user's.
 347
 348 Below this is a list of fields and you can specify a value for each. When the automatic action is run, these will set the bug's field accordingly. If a field is left blank here, then it will have no effect on the bug. If the user specifies a value for one of the fields and runs an automatic action at the same time, the automatic action will take precedence and override the user.
 349
 350 [note]If the user is in a usergroup that does not have permission to change one of the fields that is specified in the automatic action, the field will change despite this when the automatic action is run.[/note]
 351         </section>
 352
 353         <!-- =================================================================== -->
 354
 355         <section id="admin.users">
 356                 <title>User Management</title>
 357                 In Bugdar, you can control and edit the profiles of all registered users. If you want to change a user's options, simply specify a display name, email, or a user ID at this screen:
 358
 359                 <mediaobject>
 360
 361                         <imageobject>
 362
 363                                 <imagedata fileref="images/user_manage/user_search.png" format="PNG" align="center" />
 364
 365                         </imageobject>
 366
 367                 </mediaobject>
 368
 369 If more than one user matches your search criteria, you will get a listing of users that match. Otherwise, you will be redirected to the edit screen:
 370
 371                 <mediaobject>
 372
 373                         <imageobject>
 374
 375                                 <imagedata fileref="images/user_manage/user_edit.png" format="PNG" align="center" />
 376
 377                         </imageobject>
 378
 379                 </mediaobject>
 380
 381 Here, you can change all the options that the user can change in his or her profile.
 382         </section>
 383
 384         <!-- =================================================================== -->
 385
 386         <section id="admin.usergroups">
 387                 <title>Usergroups</title>
 388                 Usergroups are at the backbone of BugStrike's permissions system. There are two textual options for usergroups:
 389
 390 <strong>Usergroup Title</strong>: This is the internal name of the usergroup; it is never displayed to the users, but administrators use it to place users in groups.
 391
 392 <strong>Display Title</strong>: Under a comment poster's name, this text is placed to help distinguish regular users from developers, administrators, and guests.
 393
 394 The majority of the permissions on this page are similar to those of <link linkend="admin.usergroups.permissions">test</link> and they are explained in-depth <link linkend="admin.usergroups.permissions.reference">here</link>. Those that are not part of the usergroup permissions system are listed here.
 395
 396 <strong>Can Search Bugs</strong>: A usergroup's ability to use the search function. If this is not enabled, then searches cannot be performed by the given usergroup.
 397
 398 <strong>Can Be Assigned Bugs</strong>: If this is set to <em>Yes</em>, all the users in this usergroup will appear in the "Assigned" field drop-down menu for bug reports.
 399
 400 <strong>Can Access Control Panel</strong>: This controls whether or not users in this usergroup can login to the <link linkend="admin.about">Admin Control Panel</link>.
 401
 402 <strong>Can Administer Bug Reports</strong>: Currently, this only controls access to the <link linkend="admin.automations">Automatic Actions</link> feature.
 403
 404 <strong>Can Administer Additional Bug Fields</strong>: If this is set to <em>Yes</em>, users in this group will be able to define and edit <link linkend="admin.customfields">custom bug fields</link>.
 405
 406 <strong>Can Administer Products / Components / Versions</strong>: Allows users to define and edit <link linkend="admin.products">products, versions, and components</link>. This privilege should be sparingly given out as users can also delete products, versions, and components and thus remove all associated bugs.
 407
 408 <strong>Can Administer Users</strong>: Controls access to the <link linkend="admin.users">user manager</link> and the ability to edit and delete users.
 409
 410 <strong>Can Administer Usergroups</strong>: Setting this to <em>Yes</em> gives the users in this group the ability to control all aspects of usergroups--including permissions. Please be careful when defining this permission.
 411
 412 <strong>Can Administer Settings / Maintenance Tools</strong>: Access to this allows control of <link linkend="admin.language">languages</link> and <link linkend="admin.settings">settings</link>.
 413
 414 Additionally, the usergroup manager has the custom field permissions system, similar to the one found on the <link linkend="admin.customfields">custom field editor page</link>, the difference being that this is by field whereas the other is by usergroup.
 415
 416                 <!-- ################################################################### -->
 417
 418                 <section id="admin.usergroups.permissions">
 419                         <title>Usergroup Permissions</title>
 420                         In the <link linkend="admin.usergroups">usergroups manager</link>, you can set the default permissions that apply to every product. However, sometimes you may need finer control over the permissions.
 421
 422         Using the permissions manager, you can override the default permissions set by the usergroup.
 423
 424         The default screen shows a list of all the usergroups with an <strong>[Expand]</strong> link next to them. Clicking this link will display a list of all available products underneath the usergroup:
 425
 426                         <mediaobject>
 427
 428                         <imageobject>
 429
 430                                 <imagedata fileref="images/usergroups_permissions/expanded.png" format="PNG" align="center" />
 431
 432                         </imageobject>
 433
 434                 </mediaobject>
 435
 436         If you want to override the permissions for a certain product, simply click the <strong>[Customize]</strong> link to go to a permissions page, similar to the one in the usergroup editor. You can find an explanation of these permissions <link linkend="admin.usergroups.permissions.reference">here</link>.
 437
 438         After you have customized permissions, but you find that you no longer want the customizations, simply click the <strong>[Revert]</strong> link.
 439                 </section>
 440
 441                 <!-- ################################################################### -->
 442
 443                 <section id="admin.usergroups.permissions.reference">
 444                         <title>Permissions Reference</title>
 445                         This is a list of the permissions that can be customized on the <link linkend="admin.usergroups.permissions">per-product level</link>. These--plus some additional permissions that are not available on the product-level can be found in the <link linkend="admin.usergroups">usergroup editor</link>.
 446
 447         <strong>Can View Bugs</strong>: Permits the ability to view bugs of this product.
 448
 449         <strong>Can View Hidden Bugs and Comments</strong>: Allows viewing of bugs and comments that have been marked <em>Hidden</em>. {{NEED LINK: HIDING}}
 450
 451         <strong>Can Subscribe to Bugs</strong>: Controls the ability to add bugs of this product to the user's "favourite" list. {{NEED LINK: FAVOURITES}}
 452
 453         <strong>Can Vote on Polls</strong>: The ability to vote for a bug. Voting shows the amount of interest in a bug. {{NEED LINK: VOTING}}
 454
 455         <strong>Can Submit Bugs</strong>: Determines if users can submit bugs under this product.
 456
 457         <strong>Can Post Comments</strong>: Controls whether or not users can post comments to bugs with this product.
 458
 459         <strong>Can View Attachments</strong>: Ability to view attachments in bugs with this product.
 460
 461         <strong>Can Upload/Edit Own Attachments</strong>: Whether or not the user can edit and upload his or her own attachments to bugs with this product.
 462
 463         <strong>Can Manage All Attachments</strong>: Ability to edit other users' attachments.
 464
 465         <strong>Can Edit Own Bugs</strong>: Can edit the basic fields of bugs submitted by the user herself. The basic fields are: hidden, summary, product/component/version, severity, duplicates, and dependencies.
 466
 467         <strong>Can Edit Others' Bugs</strong>: The same as <em>Can Edit Own Bugs</em> except it applies to bugs that the user did not submit.
 468
 469         <strong>Can Edit Own Comments</strong>: Ability to edit comments submitted by the user herself to bugs with this product.
 470
 471         <strong>Can Edit Others' Comments</strong>: The same as <em>Can Edit Own Comments</em> but it applies to comments submitted by everybody who is not the current logged in user.
 472
 473         <strong>Can Assign Bugs</strong>: The ability to control the "Assigned To" field.
 474
 475         <strong>Can Change Status</strong>: Controls the ability to edit the status, resolution, and priority fields.
 476                 </section>
 477
 478         </section>
 479
 480 </chapter>