Bug 183113

Summary: Needs configurable death date
Product: [Applications] kaddressbook Reporter: Dotan Cohen <kde-2011.08>
Component: generalAssignee: Tobias Koenig <tokoe>
Status: REOPENED ---    
Severity: wishlist CC: me, tokoe, woda
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dotan Cohen 2009-02-04 01:38:41 UTC
Version:            (using KDE 4.2.0)
Installed from:    Ubuntu Packages

In addition to a birthdate and an anniversary, contacts should have a death date as well. Additionally, contacts with the death date filled in should no longer have their birthdays shown in Korganizer. This is useful, for example, when a family member dies. I want to keep his information in Kaddressbook, but I do not want to see his birthday on the calendar every year.
Comment 1 Christian Lorch 2009-08-02 11:48:52 UTC
Want to add a very strong: YESSSS!
It would be great, if additional date fields could be added. Day of death (with configurable switch to show the birthday of the dead person), Day of marriage, Day of baptism, engagement, etc.
I want to keep some information of the (dead) person, especially when s.o. is known with his complete familiy.
Comment 2 Tobias Koenig 2009-08-05 16:41:25 UTC
The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.
Comment 3 Dotan Cohen 2009-10-16 11:46:37 UTC
Moving feature request to new KAddressBook Product.
Comment 4 Jonathan Marten 2012-11-15 12:05:30 UTC
*** Bug 310130 has been marked as a duplicate of this bug. ***
Comment 5 Justin Zobel 2021-03-09 02:34:24 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.