After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 389078 - When composing a new email, clicking "To:" to open addressbook always starts in "Anniversary" category.
When composing a new email, clicking "To:" to open addressbook always starts ...
Status: RESOLVED DUPLICATE of bug 355271
Product: evolution
Classification: Applications
Component: Contacts
2.8.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-12-24 01:04 UTC by Rob van der Linde
Modified: 2008-07-08 06:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Rob van der Linde 2006-12-24 01:04:49 UTC 
I am using Evolution 2.8 on Ubuntu Edgy. When I compose a new message, and click the "To:" button, to open the address book, it opens the contacts window, but it always starts in the topmost category, being "Anniversary". There is nothing in this category, so shows no contacts, you then always have to select "Any Category" to continue. This is not really a bug, but it's an extra click, and a bit inconvenient.

I think it will be more user friendly, if you open the contacts window, by default it always starts in "Any Category". This reduces the amount of clicks, and will show all contacts as soon as you open the address book.

Other information:
Comment 1 Øystein Gisnås 2007-04-22 20:11:56 UTC 
I can't reproduce this in 2.10.1. Can you verify, please?
Comment 2 Øystein Gisnås 2007-04-22 21:12:05 UTC 
This problem has been already been reported in bug #355271.
Comment 3 Akhil Laddha 2008-07-08 06:38:02 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.


*** This bug has been marked as a duplicate of 355271 ***