113
113
NAME="emailsettings"
114
>3.3.2. Email Settings</A
117
>On this tab you can reduce or increase the amount of email sent
118
you from Bugzilla, opting in our out depending on your relationship to
119
the bug and the change that was made to it. (Note that you can also do
120
client-side filtering using the X-Bugzilla-Reason header which Bugzilla
121
adds to all bugmail.)</P
123
>By entering user email names, delineated by commas, into the
124
"Users to watch" text entry box you can receive a copy of all the
125
bugmail of other users (security settings permitting.) This powerful
126
functionality enables seamless transitions as developers change
127
projects or users go on holiday.</P
142
SRC="../images/note.gif"
149
>The ability to watch other users may not be available in all
150
Bugzilla installations. If you can't see it, ask your
162
NAME="footersettings"
163
>3.3.3. Page Footer</A
166
>On the Search page, you can store queries in Bugzilla, so if you
167
regularly run a particular query it is just a drop-down menu away.
168
Once you have a stored query, you can come
169
here to request that it also be displayed in your page footer.</P
114
>6.10.2. Email Settings</A
117
> This tab controls the amount of email Bugzilla sends you.
120
> The first item on this page is marked <SPAN
122
>"Users to watch"</SPAN
124
When you enter one or more comma-delineated user accounts (usually email
125
addresses) into the text entry box, you will receive a copy of all the
126
bugmail those users are sent (security settings permitting).
127
This powerful functionality enables seamless transitions as developers
128
change projects or users go on holiday.
144
SRC="../images/note.gif"
151
> The ability to watch other users may not be available in all
152
Bugzilla installations. If you don't see this feature, and feel
153
that you need it, speak to your administrator.
160
> In general, users have almost complete control over how much (or
161
how little) email Bugzilla sends them. If you want to receive the
162
maximum amount of email possible, click the <SPAN
166
> button. If you don't want to receive any email from
167
Bugzilla at all, click the <SPAN
169
>"Disable All Mail"</SPAN
186
SRC="../images/note.gif"
193
> Your Bugzilla administrator can stop a user from receiving
194
bugmail by adding the user's name to the
198
> file. This is a drastic step
199
best taken only for disabled accounts, as it overrides the
200
the user's individual mail preferences.
207
> If you'd like to set your bugmail to something besides
208
'Completely ON' and 'Completely OFF', the
211
>"Field/recipient specific options"</SPAN
213
allows you to do just that. The rows of the table
214
define events that can happen to a bug -- things like
215
attachments being added, new comments being made, the
216
priority changing, etc. The columns in the table define
217
your relationship with the bug:
225
> Reporter - Where you are the person who initially
226
reported the bug. Your name/account appears in the
235
> Assignee - Where you are the person who has been
236
designated as the one responsible for the bug. Your
237
name/account appears in the <SPAN
239
>"Assigned To:"</SPAN
246
> QA Contact - You are one of the designated
247
QA Contacts for the bug. Your account appears in the
251
> text-box of the bug.
256
> CC - You are on the list CC List for the bug.
257
Your account appears in the <SPAN
266
> Voter - You have placed one or more votes for the bug.
267
Your account appears only if someone clicks on the
270
>"Show votes for this bug"</SPAN
289
SRC="../images/note.gif"
296
> Some columns may not be visible for your installation, depending
297
on your site's configuration.
304
> To fine-tune your bugmail, decide the events for which you want
305
to receive bugmail; then decide if you want to receive it all
306
the time (enable the checkbox for every column), or only when
307
you have a certain relationship with a bug (enable the checkbox
308
only for those columns). For example: if you didn't want to
309
receive mail when someone added themselves to the CC list, you
310
could uncheck all the boxes in the <SPAN
312
>"CC Field Changes"</SPAN
314
line. As another example, if you never wanted to receive email
315
on bugs you reported unless the bug was resolved, you would
316
un-check all boxes in the <SPAN
320
except for the one on the <SPAN
322
>"The bug is resolved or
340
SRC="../images/note.gif"
347
> Bugzilla adds the <SPAN
349
>"X-Bugzilla-Reason"</SPAN
351
all bugmail it sends, describing the recipient's relationship
352
(AssignedTo, Reporter, QAContact, CC, or Voter) to the bug.
353
This header can be used to do further client-side filtering.
360
> Two items not in the table (<SPAN
362
>"Email me when someone
363
asks me to set a flag"</SPAN
366
>"Email me when someone
367
sets a flag I asked for"</SPAN
368
>) define how you want to
369
receive bugmail with regards to flags. Their use is quite
370
straightforward; enable the checkboxes if you want Bugzilla to
371
send you mail under either of the above conditions.
374
> By default, Bugzilla sends out email regardless of who made the
375
change... even if you were the one responsible for generating
376
the email in the first place. If you don't care to receive bugmail
377
from your own changes, check the box marked <SPAN
380
reports of changes made by other people"</SPAN
added
removed
docs/html/userpreferences.html
