because of the initial fix for bug 26413, identity and server information is being cleared whenever you delete an account. If either the server or identity still exist in another account, the values are lost. The proper fix is to go through all other accounts and find the identity/server that's going away, and only destroy it when no other accounts are using it.
Mail Review recommends this bug as beta2 stopper. Adding nsbeta2 keyword.
I disagree that this is a beta stopper, shared identities are not supported.
Target Milestone: M17 → M18
Putting on [nsbeta2-] radar. Not critical to beta2.
massive reassign of account manager bugs -> sspitzer please feel free to put me back on the CC if you have any questions/comments
Assignee: alecf → sspitzer
Status: ASSIGNED → NEW
clearing milestone, m17 and m18 are meaningless now. these need to be triages along with the rest.
Target Milestone: M18 → ---
mass re-assign of account manager bugs to racham.
Assignee: sspitzer → racham
please fix this soon, the target milestone is set to 1.0.1...
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: normal → critical
Removing the old nsbeta2-.
Assignee: racham → sspitzer
Status: ASSIGNED → NEW
Scott, do you think that this critical bug could be fixed for Aviary1.0?
Flags: blocking-aviary1.0? → blocking-aviary1.0-
There are no steps-to-reproduce for this bug. I, at least, do not know even what a "shared identity" is, let alone how to create one -- and comment 2 (from reporter) states that shared identities are not supported. While the 'dataloss' keyword is justifiable, the 'critical' severity is not.
Priority: P3 → --
Target Milestone: mozilla1.0.1 → ---
(In reply to comment #13) > There are no steps-to-reproduce for this bug. I, at least, do not know even > what a "shared identity" is, let alone how to create one -- and comment 2 (from > reporter) states that shared identities are not supported. While there is no UI to create a shared identity, it can be easily created by hand-editing prefs.js. Just have the mail.account.accountXX.identities and mail.account.accountYY.identities both mention idZZ (for some numbers XX, YY and ZZ). Most things will actually work correctly if you do this, but some would break (this bug is one example). While hand-creating the shared identities might seem like a bad idea in the first place, the shared identities is a nice feature to have and once the bugs uncovered by such hand-creation are fixed, we might consider adding a UI for it.
You need to log in before you can comment on or make changes to this bug.