Closed Bug 340828 Opened 19 years ago Closed 19 years ago

it's impossible to search bugmail for comments by a person

Categories

(Bugzilla :: Email Notifications, defect)

2.20.1
x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: timeless, Unassigned)

Details

let me start by saying that i haven't slept in over 2 days. and i want to kill someone. probably internally, since that's bad for business, i've decided it has to be a bugzilla developer. steps to reproduce: 1. create a 3 year log of nearly all bug comments for a large bugzilla 2. over the course of 3 years, comment in thousands of bugs. 3. for kicks be sure that other people occasionally mention your email address in bugmails 4. also given the 3 years of your time, you might as well file a couple hundred or thousand bugs, it's not that expensive 5. try to track bugs down by looking for bugs you've commented in. expected results: searching for "additional comments from timeless@bemail.org" should work very well. for simplicity, searching for "from timeless" works well and is easy to type. actual results: it only works until someone got clever and screwed up the comment reporting format so that you can no longer perform this search. note that every single email in your inbox will have "timeless" in it, so searching for "timeless" as a bare word is amazingly useless. expected fix: UNDO THIS CHANGE to the bugmail format. acceptable fixes do *NOT* include adding envelope headers as GMAIL does NOT support searching envelopes. yes, i'm vaguely aware that if i'm willing to search for each year i could possibly have mode a comment, i can use "bemail.org 2006" and similar. but that's really sucky. this is a regression and it's blocking my ability to get work done in the browser project.
Not a blocker, nor a regression. You can look for "from timeless@bemail.org" if you want. If you cannot have it in one filter, add a second one.
Severity: blocker → minor
Status: NEW → RESOLVED
Closed: 19 years ago
Keywords: regression
Resolution: --- → WORKSFORME
hrm, maybe my problem was the accidental double paste of my query. which normally would be harmless, but was resulting in is:unread being in the middle of it and me not able to get things to work.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.