Closed Bug 18747 Opened 25 years ago Closed 24 years ago

[UI] need a way to distinguish between / reduce duplicate identites

Categories

(MailNews Core :: Composition, defect, P3)

Product:
MailNews Core
Component:
Composition
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 31549

People

(Reporter: sspitzer, Assigned: sspitzer)

Details

when we migrate from 4.x to 5.0, we copy the 4.x identity n times, where n is
the number of 5.0 accounts we create.  (2 news servers, 2 imap servers in 4.x
becomes 5 accounts, one more for "Local Mail", so we end up with 5 identities.)

then, when using 5.0 to send mail, we have the choice of 5 identities, all of
which look the same when trying to choose one from the compose window.

So for me, I'd see the following identities in the "from" picker:

Seth Spitzer <sspitzer@netscape.com>
Seth Spitzer <sspitzer@netscape.com>
Seth Spitzer <sspitzer@netscape.com>
Seth Spitzer <sspitzer@netscape.com>
Seth Spitzer <sspitzer@netscape.com>

do we need to show more in the from picker?

perhahs append, in italics, what differentiates between the identities?

another idea, if all the identities have the same affect (they both fcc to the
same folders, etc) then only show one identity.
I tried this in the 1999-11-12-18 M11 build.  The very first item for From:
shows "foo", followed by about 10 "Lisa Chiang's" because I migrated 10
items (mail and news) over.

If you append in italics what is different, there not be enough room in the From
drop down list.

I like your idea about only showing one identity if all the identities have the
same affect.  I think showing so many of the same names may confuse the user as
to which one to choose.
I already have a bug assigned to me for this....but now I can't find it! I think
laurel or ninoschka filed it.... searching...
ah, it's 15621.

Seth, if you're already working on this, feel free to take this. I haven't done
anything with it yet... one of these bugs should be marked a dupe of the other.
marking m15, accepting.
moving to m16.
Target Milestone: M15 → M16
QA Contact: lchiang → nbaca
Triage to M17.  Please add beta2 keyword if this must make beta2.  Please let me 
know if this must be done by M16 feature freeze.
Target Milestone: M16 → M17
Mail Review hopes this is post-beta2, easy, polish work.  Marking M18.
Target Milestone: M17 → M18
m30.  not going to happen for 6.0
Target Milestone: M18 → M30
marking dup of 31549

*** This bug has been marked as a duplicate of 31549 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
VERIFYING as dupe
(BTW may I do such stuff when not being the QA?)
Status: RESOLVED → VERIFIED
sebastian - here are some guidelines for verifying mail/news bugs if you want to 
help:  http://www.mozilla.org/quality/mailnews/mail-bug-verification.html

In this case, since it was an exact duplicate bug, your help is welcome.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.