Open Bug 86201 Opened 23 years ago Updated 12 years ago

Ability to specify what fields appear in a notification or its headers

Categories

(Bugzilla :: Email Notifications, enhancement, P3)

2.13
enhancement

Tracking

()

People

(Reporter: CodeMachine, Unassigned)

References

Details

(Keywords: ue)

We need to be able to let users specify what fields they want to appear on
notifications.

There are plenty of bugs that I will mark as a duplicate of this one that ask
for certain fields to always appear.  This bug is about a general proposal for a
user to select which of these they would like.

Even more generally, we might allow three options for each field:  Always
Show/Never Show/Show Only When Changed.
*** Bug 3156 has been marked as a duplicate of this bug. ***
*** Bug 28938 has been marked as a duplicate of this bug. ***
For list fields (CC, keywords, etc) we should split "Show Only When Changed"
Into "Show Changes When Changed" and "Show All When Changed".

Target Milestone: --- → Bugzilla 2.16
Priority: -- → P3
In case it wasn't obvious, "Never Show" is important because even though that
field might never trigger a notification, it could still appear on e-mails where
something else triggered a notification.

If you really don't care about that field (for example the way some people don't
care at all about CC), this would make their lives simpler.
-> Bugzilla product, Email component, reassigning.
Assignee: tara → jake
Component: Bugzilla → Email
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13
*** Bug 98062 has been marked as a duplicate of this bug. ***
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
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
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
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
Assignee: preed → email-notifications
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
*** Bug 301430 has been marked as a duplicate of this bug. ***
(In reply to comment #0)
>....
>
> Even more generally, we might allow three options for each field:  Always
> Show/Never Show/Show Only When Changed.


I would think that a checkbox grid (similar to the one in the eMail section of Preferences) might be more intuitive.  Each row in the grid would represent a field, each column would represent a place where that field could appear.  If the check box is "checked" then that field would appear in that location.

Some examples of locations might be:

 New bug email
 Changed bug email
 Whine email

etc.

This method of configuring 'which fields appear where' might even be expanded to have a column for, e.g., the New Bug Entry page, etc.
Keywords: ue
i presume this also includes bugmail headers
Summary: Ability to specify what fields appear on a notification. → Ability to specify what fields appear in a notification or its headers
You need to log in before you can comment on or make changes to this bug.