Closed
Bug 71687
Opened 23 years ago
Closed 23 years ago
auto-excluding myself sometimes doesn't work
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
People
(Reporter: hwaara, Assigned: justdave)
Details
Sometimes when I comment in a bug and then hits "Commit" the table that is displayed tells me that I'm not excluded and I get my own bug-comment in the mail, which I'm not supposed to do. Because I have the "Exclude myself" checkbox checked in the Bugzilla prefs. This started happening with the recent Bugzilla update, so the must've messed up somehow since 2.10
Comment 1•23 years ago
|
||
Do you have any watches set up?
Assignee | ||
Comment 3•23 years ago
|
||
Håkan, if you are watching anyone, this is a duplicate of bug 71550. Can you confirm?
Reporter | ||
Comment 4•23 years ago
|
||
Well, I watch 3 persons... But I don't understand what that has to do with the problem? (This is probably a duplicate, but please explain why the watching makes any difference when I'm posting in BZ.)
Comment 5•23 years ago
|
||
There is currently a confirmed (but as of yet unfixed) bugs where if: User A watches user B User A is set to not recieve self changes User A makes a change to a bug that user B is CC'd on (or rep. own. qa.) Then User A will get the mail anyway ('cause they watch B and B got it). So, if one of the three ppl you watch are recieving mail about the bug you change, you'll get the message to. That's where bug 71550 comes into play.
Updated•23 years ago
|
Target Milestone: --- → Bugzilla 2.12
Updated•23 years ago
|
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 7•23 years ago
|
||
OK, this was most likely a result of bug 71550. Bug 74996 has been filed at Håkan's request to have watching get it's own category *** This bug has been marked as a duplicate of 71550 ***
Assignee | ||
Comment 9•23 years ago
|
||
clearning milestone on resolved non-FIXED bugs in case they ever get reopened.
Target Milestone: Bugzilla 2.12 → ---
Assignee | ||
Comment 10•23 years ago
|
||
moving all closed Bugzilla bugs to the new Bugzilla product. This batch is DUPLICATE/INVALID/WORKSFORME/WONTFIX reassigning to default owner and QA in case of the bug being reopened. Clearing milestones, since we really shouldn't have them on these types of resolutions. Sorry for the spam everyone...
Assignee: tara → justdave
Status: VERIFIED → NEW
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → unspecified
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•