Bug 316143 - System does not display (More than one?) Upcoming Special dates
Summary: System does not display (More than one?) Upcoming Special dates
Status: RESOLVED DUPLICATE of bug 327256
Alias: None
Product: kontact
Classification: Applications
Component: summary (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-04 21:42 UTC by Frans Leerink
Modified: 2014-08-05 10:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frans Leerink 2013-03-04 21:42:26 UTC
In my contacts I have the birthday of my sister and brother entered and the summary configuration specify that all Upcoming special dates should be reported for the coming 7 days.

It is now monday and to morrow is my sisters birthday and my brothers birthday is coming saturday.
1 With the mentioned settings only my brothers birtday is shown as Upcoming Special date.
2 I have changed the configuration step by step from 7 to 1 days (and shutdown and restarted Kontact) and with 4, 3, 2 and 1days the system displayed my sisters birthday  as Upcoming Special date. With 7, 6 and 5 days my brothers birtday is shown as Upcoming Special date.

Reproducible: Always

Steps to Reproduce:
1. Create 2 contacts with birthdays tomorrow and the other 4 days later.
2. Configure kontact-summary-UpcomingSpecialDates with 7 days
3 Shutdown/restart Kontact and check which Upcoming Special Date is displayed 
Actual Results:  
System shows only the 4 days later one and continue to do that until the configuration is reduced to 4 days or less and then the system shows the Tomorrow special date

Expected Results:  
Should display  both Upcoming Special dates.
Comment 1 Wolfgang Bauer 2014-08-05 10:14:31 UTC
This seems to be a duplicate of bug#327256.

Please reopen if you disagree.

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