Provide easy way to disable all email ("vacation mode")

NEW
Unassigned

Status

()

Bugzilla
Email Notifications
P3
enhancement
17 years ago
12 years ago

People

(Reporter: Cesar Eduardo Barros, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

17 years ago
There are more than 20 checkboxes in the email preferences. If you have many of
them checked, have a limited space in your mailbox, and will be for some time
(say, a week) away from any computer access (what people usually call
"vacation"), you have to uncheck all of them. Then, when you are back, you have
to reenable them all, trying to remember how they were set before.

It would be much easier if there was another checkbox to act as a "global
disable" (vacation mode), which would make bugzilla act as if all checkboxes
were disabled, without actually disabling them (so if you unchecked it, it would
bring you back to your custom email notification settings).
Changing default owner of Email Notifications component to JayPee, a.k.a.
J. Paul Reed (preed@sigkill.com).  Jake will be offline for a few months.
Assignee: jake → preed
Priority: -- → P3
Target Milestone: --- → Future

Updated

15 years ago
OS: Linux → All
Hardware: PC → All

Comment 2

13 years ago
Kick all my Bugzilla bugs back to the component default owner.
Assignee: preed → email-notifications

Comment 3

12 years ago
It seems to me, we really need to address a bigger issue here.  When users are on vacation / sabbatical, typically, they not only don't want emails, but they also don't want assignments.  It seems to me that we ought to have a way of dealing with "user is away" and have a method of storing (and automatically re-enabling) when a user plans to return.  I think this should be a user-level function that administrators can set if needed.  If you're thinking use the disabled text, that still doesn't solve the problem of emails or automatically re-enabling the user when they return.

Updated

12 years ago
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Future → ---
You need to log in before you can comment on or make changes to this bug.