Closed Bug 645941 Opened 13 years ago Closed 13 years ago

bugzilla account merge

Categories

(bugzilla.mozilla.org :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: nmeyerhans, Assigned: justdave)

Details

I have an ancient bugzilla account (noahm@lcs.mit.edu) that keeps getting accidentally added to the CC list for current bugs.  Can that account be merged with my current one? (nmeyerhans@mozilla.com)
What if we just disabled the old account and make sure it is not set up as default cc for any components? Would that be sufficient? Or are there bugs that your old account is associated with that you still want to track?

justdave, can you check to see what components the noahm@lcs.mit.edu account is possibly default cc'ed on? 

Dave
Assignee: nobody → dkl
Status: NEW → ASSIGNED
I think it'd be perfectly reasonable to disable noahm@lcs.mit.edu as a default CC for anything in the future.  As long as that'll prevent bugzilla from suggesting that address as a completion option when people type "noahm" into the CC field.
(In reply to comment #2)
> I think it'd be perfectly reasonable to disable noahm@lcs.mit.edu as a default
> CC for anything in the future.  As long as that'll prevent bugzilla from
> suggesting that address as a completion option when people type "noahm" into
> the CC field.

Sorry for letting this go so long. 

Justdave, are we able to run the merge account script on these two accounts so we can disable the old one?

Noah, when we set the old account to disable, it will not show up in the auto complete list AFAIK.

dkl
Assignee: dkl → justdave
Posting from noahm@lcs.mit.edu to confirm that this account is mine and that the request in this bug is valid. Please either de-activate or merge noahm@lcs.mit.edu with nmeyerhans@mozilla.com. Thanks.
Done.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.