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 271592 - Contact with birthday and anniversary only displays birthday in calendar.
Contact with birthday and anniversary only displays birthday in calendar.
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: vivek jain
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-01-21 22:33 UTC by Paul Bryan
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fixes the problem (1.73 KB, patch)
2005-05-12 13:36 UTC, vivek jain
none Details | Review

Description Paul Bryan 2005-01-21 22:33:41 UTC
Description of Problem:
When a contact has both a birthday and an
anniversary set, only the birthday is displayed in
the calendar; anniversary is not displayed. They
do not have to share the same date.

Steps to reproduce the problem:
1. Create a contact.
2. Add anniversary to contact.
3. Verify anniversary is displayed in calendar.
4. Add birthday to contact.
5. Verify anniversary disappears in calendar.
6. Verify birthday is displayed in calendar.

Actual Results:
Birthday displayed in calendar; anniversary not.

Expected Results:
Birthday and anniversary should both display in
calendar if they are set on a contact.

How often does this happen? 
Always.
Comment 1 Sivaiah 2005-02-19 14:47:35 UTC
probably a prolem with contacts calendar backend. chaing component
Comment 2 Kayhan Gultekin 2005-05-05 01:22:44 UTC
This probably doesn't help at all, but the bug also exists in 2.0.4
Comment 3 vivek jain 2005-05-12 13:36:17 UTC
Created attachment 46367 [details] [review]
fixes the problem
Comment 4 vivek jain 2005-05-12 13:37:07 UTC
Fix Committed to CVS head.
Comment 5 Paul Bryan 2006-01-12 02:42:39 UTC
Confirmed that this is fixed in version 2.4.2.1.