when accounts are deleted, shared identities/servers should not be erased

NEW
Unassigned

Status

SeaMonkey
MailNews: Account Configuration
--
critical
18 years ago
6 years ago

People

(Reporter: Alec Flett, Unassigned)

Tracking

({dataloss})

Trunk
x86
Linux
dataloss
Bug Flags:
blocking-aviary1.0 -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
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.
(Reporter)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: M17

Updated

18 years ago
QA Contact: lchiang → nbaca

Comment 1

18 years ago
Mail Review recommends this bug as beta2 stopper.  Adding nsbeta2 keyword.
Keywords: nsbeta2
(Reporter)

Comment 2

18 years ago
I disagree that this is a beta stopper, shared identities are not supported.
Target Milestone: M17 → M18

Comment 3

18 years ago
Putting on [nsbeta2-] radar. Not critical to beta2.
Whiteboard: [nsbeta2-]
(Reporter)

Updated

18 years ago
Blocks: 44863
(Reporter)

Comment 4

18 years ago
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

Updated

17 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0.1

Updated

16 years ago
Keywords: nsbeta2

Updated

16 years ago
Keywords: dataloss

Comment 7

16 years ago
please fix this soon, the target milestone is set to 1.0.1...

Comment 8

15 years ago
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

Comment 9

15 years ago
Removing the old nsbeta2-.
Whiteboard: [nsbeta2-]
mass re-assign.
Assignee: racham → sspitzer
Status: ASSIGNED → NEW
Scott, do you think that this critical bug could be fixed for Aviary1.0?
Flags: blocking-aviary1.0?

Comment 12

14 years ago
no
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail

Comment 13

11 years ago
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 → ---

Comment 14

11 years ago
(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.
QA Contact: nbaca
You need to log in before you can comment on or make changes to this bug.