+35248

We are using one calendar to create visibility for out of office times and leave. Naturally there are many events in the calendar.

It is somehow bad to see that the calendar plugin is not supporting a use case like ours for performance reasons.

The plugin is not cheap! It should have been built with performance in mind!

@Atlassian: Fix this issue!

Any movement on this issue? Thanks!

Great plugin, but performance issues due to calendar growth get blocking after a while.

we also bought this teamcal plugin... we don`t talk about a feature in this issue, we are very happy with the functionality but please solve the performance issues or implement the archiv function soon. thx a lot from switzerland.

This is becoming more and more of a problems as our use of team calendar is exploding. It seems that with the additional usage. . . it is getting much slower.

This has become a significant problem for us. We have not had the plugin for even a year. It is requiring almost a minute to save any action and for the modal to dismiss. It is unfortunate that we have to delete a calendar and start over, losing all history (which, for some calendars we cannot due to ISO quality record retention of 2 years). This should be a critical improvement that team should be focused on - e.g. when the product becomes unusable or affecting user productivity, they stop using it; when they stop using it, we identify other solutions and stop paying maintenance/support since there is no value. There definitely needs to be options for each calendar to delete events older than xx days or archive events older than xx days.

archiving is what we were hoping you guys would provide for two reasons:

1. There is currently a limit to the number of events allowed per calendar, we hit that limit on many of our calendars os events get filtered out which is not the best solution.
2. Performance - seems like removing the old events would help for now but doing indexing is really what we need, we run this in a large enterprise and slow performance is turning people off using it.

For the archive, what if you allowed:
1. a admin control to archive events past due by XX number of days (for example, archive events older than 30 days and also allow delete events older than 90 days)
2. Calendar level controls so you can set this at the individual calendar level.

We have the same issues as Scott mentioned above, my staff has really started to use TC, we have 1 group creating 5-10 events per day to track trading changes, etc. We quickly hit the limit and events started to roll off the calendar, now they don't trust the system. I increased the default to 500 but that will only hold them for a month or two.

This has become a major problem for us for our maintenance and outages calendar. We are thinking about breaking down separate calendars per month, but that would be tedious for users (we have these calendars displayed in many places throughout confluence. Changing all of those embedded calendars would be rough. The ability to purge past events would be crucial.