Ya, it would still be good to correct it so people who don't manage the 'hide alias' attributes would still get decent behavior - see edit ^ in my post just before your last.
Wanna make that 5th RFE "Hide aliases on to: field GAL auto complete if existing match for an account is found" to help get decent behavior when people don't manage the 'hide alias' attribute that's going to come out of 14919?
Just created bug 23298. I'm not sure about your comment "if existing match for an account is found". Since an alias is only an email address when you are auto-completing by name there will always be a match. Also, I consider this a bug, not an RFE, unless someone can explain to me why you would want the aliases to appear. This is especially true since it represents a change in behavior from 4.5.x, that was not noted anywhere, at least that I can find, in the release notes.Wanna make that 5th RFE "Hide aliases on to: field GAL auto complete if existing match for an account is found" to help get decent behavior when people don't manage the 'hide alias' attribute that's going to come out of 14919?
Don't remember what I was thinking...might have been mixing thoughts of some type.
In in the addressbook they're nicely grouped, but for the auto-complete what really would be cool is if a way was found to combine them into one drop down entry (showing one account per line with all the matching/searched aliases on the same line).
Mockup attached (aliasCurrentV5Compose.png vs aliasMatchesFromSameAccountOnOneLine.png):
& while we're at it...I've had someone complain about the fact that you can't select aliases in the address picker - lol (aliasCantSelectOtherAddress.png):
I've upgraded our NE from 4.5.9 tonight to 5.0.0 and have the same issue, when a user now goes to compose a new message in the To field auto-complete is showing all aliases this will be very annoying when my uses come back on Monday.
I want it to behave as it did in 4.5.x, alot of my users have 3 to 4 aliases.
jholder um I looked at that bug listing and the last entry says "fixed in 5.0", but thats what I am using and its not fixed.