Bug 105728 - wish: ability to specify which resources are used in kontact appointment summary
Summary: wish: ability to specify which resources are used in kontact appointment sum...
Status: CONFIRMED
Alias: None
Product: kontact
Classification: Applications
Component: summary (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 169909 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-05-15 22:28 UTC by Andy Neitzke
Modified: 2010-12-08 12:48 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Neitzke 2005-05-15 22:28:25 UTC 
Version:            (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages

I am using KOrganizer to store my personal calendar and also a work related calendar which contains many more events.  I always want only my personal calendar to appear in the summary page, irrespective of which resource I may be working with in the calendar page. 

On my system, using Kontact 1.1 / KOrganizer 3.4, it seems that the "appointments" which appear on the summary page are always drawn from the same set of resources that are currently activated in the calendar page.  It would be useful if they could be configured independently.
Comment 1 Dotan Cohen 2008-03-23 21:03:40 UTC 
Agreed. The summary page is just that: a summary. The data it shows should be consistent, regardless of what filters or resources the user is doing at any given moment in each application's tab. The resource that the summary uses should be configurable in the Configuration menu, and remain how they are configured even when the user applies filters or different resources to the calender app.
Comment 2 Christophe Marin 2009-08-20 21:34:08 UTC 
*** Bug 191286 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2010-12-08 12:48:48 UTC 
*** Bug 169909 has been marked as a duplicate of this bug. ***