TEXT   6

User Preferences

Guest on 6th July 2022 08:47:16 AM

  1. User Preferences
  2. ****************
  4. Once logged in, you can customize various aspects of Bugzilla via the
  5. "Preferences" link in the page footer. The preferences are split into
  6. a number of tabs, detailed in the sections below.
  9. General Preferences
  10. ===================
  12. This tab allows you to change several default settings of Bugzilla.
  13. Administrators have the power to remove preferences from this list, so
  14. you may not see all the preferences available.
  16. Each preference should be self-explanatory.
  19. Email Preferences
  20. =================
  22. This tab allows you to enable or disable email notification on
  23. specific events.
  25. In general, users have almost complete control over how much (or how
  26. little) email Bugzilla sends them. If you want to receive the maximum
  27. amount of email possible, click the "Enable All Mail" button. If you
  28. don't want to receive any email from Bugzilla at all, click the
  29. "Disable All Mail" button.
  31. Note: A Bugzilla administrator can stop a user from receiving
  32.   bugmail by clicking the "Bugmail Disabled" checkbox when editing the
  33.   user account. This is a drastic step best taken only for disabled
  34.   accounts, as it overrides the user's individual mail preferences.
  36. There are two global options -- "Email me when someone asks me to set
  37. a flag" and "Email me when someone sets a flag I asked for". These
  38. define how you want to receive bugmail with regards to flags. Their
  39. use is quite straightforward: enable the checkboxes if you want
  40. Bugzilla to send you mail under either of the above conditions.
  42. If you'd like to set your bugmail to something besides 'Completely ON'
  43. and 'Completely OFF', the "Field/recipient specific options" table
  44. allows you to do just that. The rows of the table define events that
  45. can happen to a bug -- things like attachments being added, new
  46. comments being made, the priority changing, etc. The columns in the
  47. table define your relationship with the bug - reporter, assignee, QA
  48. contact (if enabled) or CC list member.
  50. To fine-tune your bugmail, decide the events for which you want to
  51. receive bugmail; then decide if you want to receive it all the time
  52. (enable the checkbox for every column) or only when you have a certain
  53. relationship with a bug (enable the checkbox only for those columns).
  54. For example, if you didn't want to receive mail when someone added
  55. themselves to the CC list, you could uncheck all the boxes in the "CC
  56. Field Changes" line. As another example, if you never wanted to
  57. receive email on bugs you reported unless the bug was resolved, you
  58. would uncheck all boxes in the "Reporter" column except for the one on
  59. the "The bug is resolved or verified" row.
  61. Note: Bugzilla adds the "X-Bugzilla-Reason" header to all bugmail it
  62.   sends, describing the recipient's relationship (AssignedTo,
  63.   Reporter, QAContact, CC, or Voter) to the bug. This header can be
  64.   used to do further client-side filtering.
  66. Bugzilla has a feature called "User Watching". When you enter one or
  67. more comma-delineated user accounts (usually email addresses) into the
  68. text entry box, you will receive a copy of all the bugmail those users
  69. are sent (security settings permitting). This powerful functionality
  70. enables seamless transitions as developers change projects or users go
  71. on holiday.
  73. Each user listed in the "Users watching you" field has you listed in
  74. their "Users to watch" list and can get bugmail according to your
  75. relationship to the bug and their "Field/recipient specific options"
  76. setting.
  78. Lastly, you can define a list of bugs on which you no longer wish to
  79. receive any email, ever. (You can also add bugs to this list
  80. individually by checking the "Ignore Bug Mail" checkbox on the bug
  81. page for that bug.) This is useful for ignoring bugs where you are the
  82. reporter, as that's a role it's not possible to stop having.
  85. Saved Searches
  86. ==============
  88. On this tab you can view and run any Saved Searches that you have
  89. created, and any Saved Searches that other members of the group
  90. defined in the querysharegroup parameter have shared. Saved Searches
  91. can be added to the page footer from this screen. If somebody is
  92. sharing a Search with a group they are allowed to assign users to, the
  93. sharer may opt to have the Search show up in the footer of the group's
  94. direct members by default.
  97. Account Information
  98. ===================
  100. On this tab, you can change your basic account information, including
  101. your password, email address and real name. For security reasons, in
  102. order to change anything on this page you must type your *current*
  103. password into the "Password" field at the top of the page. If you
  104. attempt to change your email address, a confirmation email is sent to
  105. both the old and new addresses with a link to use to confirm the
  106. change. This helps to prevent account hijacking.
  109. API Keys
  110. ========
  112. API keys allow you to give a "token" to some external software so it
  113. can log in to the WebService API as you without knowing your password.
  114. You can then revoke that token if you stop using the web service, and
  115. you don't need to change your password everywhere.
  117. You can create more than one API key if required. Each API key has an
  118. optional description which can help you record what it is used for.
  120. On this page, you can unrevoke, revoke and change the description of
  121. existing API keys for your login. A revoked key means that it cannot
  122. be used. The description is optional and purely for your information.
  124. You can also create a new API key by selecting the checkbox under the
  125. 'New API key' section of the page.
  128. Permissions
  129. ===========
  131. This is a purely informative page which outlines your current
  132. permissions on this installation of Bugzilla.
  134. A complete list of permissions in a default install of Bugzilla is
  135. below. Your administrator may have defined other permissions. Only
  136. users with *editusers* privileges can change the permissions of other
  137. users.
  139. admin
  140.    Indicates user is an Administrator.
  142. bz_canusewhineatothers
  143.    Indicates user can configure whine reports for other users.
  145. bz_canusewhines
  146.    Indicates user can configure whine reports for self.
  148. bz_quip_moderators
  149.    Indicates user can moderate quips.
  151. bz_sudoers
  152.    Indicates user can perform actions as other users.
  154. bz_sudo_protect
  155.    Indicates user cannot be impersonated by other users.
  157. canconfirm
  158.    Indicates user can confirm a bug or mark it a duplicate.
  160. creategroups
  161.    Indicates user can create and destroy groups.
  163. editbugs
  164.    Indicates user can edit all bug fields.
  166. editclassifications
  167.    Indicates user can create, destroy and edit classifications.
  169. editcomponents
  170.    Indicates user can create, destroy and edit products, components,
  171.    versions, milestones and flag types.
  173. editkeywords
  174.    Indicates user can create, destroy and edit keywords.
  176. editusers
  177.    Indicates user can create, disable and edit users.
  179. tweakparams
  180.    Indicates user can change Parameters.
  182. ======================================================================
  184. This documentation undoubtedly has bugs; if you find some, please file
  185. them here.

Raw Paste

Login or Register to edit or fork this paste. It's free.