Mark bugs newly assigned to a person with high priority

RESOLVED WONTFIX

Status

()

Bugzilla
Email Notifications
P3
enhancement
RESOLVED WONTFIX
17 years ago
10 years ago

People

(Reporter: Aaron Leventhal, Unassigned)

Tracking

Details

(Reporter)

Description

17 years ago
When I receive new bugmails, I would like my email client to show a high
priority mark next to those that are notifications of a bug being assigned to me.

Comment 1

17 years ago
My plan is to first fix bug 69399 giving the New status its own category.  Then 
at some point in the future, I'd like to give the ability to instead of just 
saying 'Yes' or 'No' to bugmail, give choices of:
( ) No
( ) Low Priority
(*) Normal Priority
( ) High Priority

Of course, that UI is far from complete, but that's the general idea.
Depends on: 69399

Comment 2

17 years ago
too bad we can't let people upload css policies. but if we can tag bugs w/ 
statuses then can't they use filters to set priorities?
Version: 2.10 → 2.15

Comment 3

17 years ago
Some e-mail clients would let you say:
If <Subject> contains "] New: " then <Set Priority to High>

I don't know if Mozilla does, but I know (please don't laugh :) MS Outlook does.

But in the end, I'd still like to be able to do make it a server side pref to
set priority on certain bugmail (based on filtering category).  After
product/keyword/etc. watching is in place, that will allow you to "watch" the
patch keyword and have any bugmail regarding that keyword come in as high priority.
This should be tacked onto the email prefs.  Each type of change has various
options - high, normal, low, not interested.
*** Bug 42409 has been marked as a duplicate of this bug. ***
Severity: normal → enhancement
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.20
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
We need to balance the flexibility people want with the need to not further
complicate the interface for novices.  My suggestion is as follows.

The user has one or more notification classes.  Each notification class has a
name, a priority, and maybe other stuff.

If there is only one notification class set up (which is the default for new
users), they will receive a checkbox as they do now, which distinguishes from
receiving no mail and receiving mail as per the notification class.

If they have multiple notification classes set up, they receive a drop down box
choosing between all the notification classes, plus no receiving.

Notification classes aren't just for priorities, they also appear in mail
headers and can be filtered upon.  In particular, they are a solution to
allowing filtering in the presence bulk changes in one email (bug #26943).

The whole idea is discussed over at bug #14137.

Updated

15 years ago
OS: Windows 2000 → All
Hardware: PC → All
Both Outlook and Mozilla allow you to change the priority of an email based on
subject or body text. So just set priority to high if the body contains 
"AssignedTo: my@mycompany.com"

Suggest WONTFIX, therefore. This would complicate the email prefs UI, which is
complex enough.

Gerv
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22

Updated

13 years ago
Assignee: preed → email-notifications
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---

Comment 10

10 years ago
(In reply to comment #8)
> Suggest WONTFIX, therefore. This would complicate the email prefs UI, which is
> complex enough.

Yeah, we don't need a UI to define the priority of bugmail, especially when the email client can do it itself based on the user wishes.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.