Don't include everconfirmed in notifications.

NEW
Unassigned

Status

()

P4
enhancement
18 years ago
3 years ago

People

(Reporter: CodeMachine, Unassigned)

Tracking

Details

(Reporter)

Description

18 years ago
I fail to see why we should include "everconfirmed" in email notifications.

AFAICS the only time it gets changed is when the status goes from UNCONFIRMED to
NEW, so it doesn't provide any useful information.

It is also potentially confusing as it is not necessarily obvious to those not
in the technical elite what "0" and "1" refer to.

Comment 1

18 years ago
Sounds reasonable to me... to do this we would have to make process_bug.cgi not
record everyconfirmed in the bugs activity table (also something that seems
reasonable).
(Reporter)

Updated

18 years ago
Target Milestone: --- → Bugzilla 2.16
(Reporter)

Updated

18 years ago
Priority: -- → P4
moving to Bugzilla product
Assignee: tara → jake
Component: Bugzilla → Email
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13
(Reporter)

Comment 3

17 years ago
I'm inclined to say we should log them, but not show them unless you pass an
undocumented parameter to the bug activity CGI.
(Reporter)

Comment 4

17 years ago
When we do customised statuses (bug #101179), this might present information
that is not obvious from a status change.
(Reporter)

Comment 5

17 years ago
Moving off because of this until we know the situation better.
Target Milestone: Bugzilla 2.16 → 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
Severity: minor → enhancement
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 8

5 years ago
Is "everconfirmed" still sent in email notifications?  I haven't noticed it on BMO, at least, although I know BMO has some customizations to email.
Flags: needinfo?(justdave)

Comment 9

3 years ago
(In reply to Mark Côté [:mcote] from comment #8)
> Is "everconfirmed" still sent in email notifications?

Yes
Flags: needinfo?(justdave)
Whether or not a field is included in an email notification is separate from whether it's displayed in the history, right? (or am I only thinking of new bugs not changes?)  I'd see no reason not to remove it from the email notification.
You need to log in before you can comment on or make changes to this bug.