I'd like each person in our company to have their own personal calendar where they can store their time off and other personal events. I then want to be able to have different project teams and direct line management groups to be able to add these people to their team or line calendar. This would help each person to not have to update mulitple calendars with their time off events.
My only hesitation is I need to know how many calendars can be layered in a single Confluence page. I'm thinking that there'd only be like 40 max for our biggest direct line management group.
Also, can Team Calendars handle 400+ calendars?
Let me see if I understand what you are trying to do. Each user has a personal calendar with their time-off etc on it. Then you would have a page with a calendar macro for each line-manager. The calendar macro would have the personal calendar for each user in that group on it. Is that right?
400+ calendars will probably work as long as they are not all added to a single macro or anyones MyCalendars view.
On a slightly differnet note it sounds like you would like the ability to create calendars that are collections of smaller calendars?
You are correct in your understanding. I'm really looking for a way to aggregate smaller calendars into a larger calendar so managers (whether they be PMs or Line Managers) have a single pane of glass to view people's time.
Currently, I have to update 8 different calendars with my time off because I cross so many different groups.
Another similar use case, is overlaying different country holidays onto your project calendar. We have 10 different country holidays we need to keep track of in our calendars. On some projects, we may only have team members from 2 countries so we don't need every countries holidays. It would be nice to have each countries holidays as separate calendars and then group only the relevant ones.
We have implemented the holiday calendars as I described, but I'm fearful of performance issues with individual user calendars.
Thanks for the answer!
I don't mean to hijack this thread but we're running into an issue where we're getting the "Some events were not shown in the calendars below because there were too many of them" message. What exactly consitutes a "view"? We have a general Engineering calendar (a People calendar) that's used for things such as working from home, out of the office, etc. While the calendar as a whole has over 200 events, the view that I'm using, week, only has about 20 events but I still get the message. Is a "view" considered to be the entire calendar? Also, which events are not being shown? The ones that are furthest out? The ones that already happened? Thanks!
By default, it's 200 events per calendar in each view. If there were too many of them, this message will appear: "Some events were not shown in the calendars below because there were too many of them"
To eliminate the message, you can change to a different maximum by specifying the system property and then restart Confluence: "com.atlassian.confluence.extra.calendar3.display.events.calendar.maxpercalendar"
By default, it's 200 events per calendar. Note that this limit applies to all events in one calendar, and not just the events that are displayed on screen.
It may have something to do with the calendar being stored as a single file in the bandana table instead of in its own database table.
So no real solution here, options being:
* manually delete past events which is time consuming,
* delete and recreate the calendar but you lose all of the history and all of the calendar subscribers,
* don't use team calendars when there are lots of events.
Hi Community! 2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs