Allow users to specify additional calendars per calendar instance or at least fname
Description
Environment
None
Activity
Show:
James Wennmacher
February 25, 2016 at 5:23 PM
Clarification of current behavior.
Effectively the calendar portlet can have one instance for a user. If you have two instances that appear on a user's layout
Both instances show the same events
If as a user you edit one calendar and either add a new personal calendar or show or hide a predefined (administrator-defined) calendar, both calendars will reflect the same data.
Also FYI there is a difference between the show/hide when you do Edit Calendars (saves and applies to next login) and when you click the show/hide after you click the link "View more events" (applies that that calendar instance but ONLY for that session, will be lost next time you log in).
James Wennmacher
February 16, 2016 at 8:29 PM
Linked to related issues that Calendar does not have per-fname settings.
Details
Details
Assignee
Unassigned
UnassignedReporter
James Wennmacher
James Wennmacher(Deactivated)Fix versions
Priority
Created February 16, 2016 at 8:29 PM
Updated July 7, 2017 at 6:18 PM
Create two calendar instances, say calendar1 and calendar2 and put both on a layout.
When a user goes into calendar1 and adds a calendar, the new user calendar displays on both calendar1 and calendar2. There is not a per-fname or per-instance configuration.
This is related to CAP-192: Support config mode for admin hiding pre-configured calendars per calendar fnameOpen and CAP-193.
Either store new calendars in an array of portlet preferences (which would be instance-based), or modify the database to support a different calendar per fname.