Index
[Downloads (PDF, HTML & XML formats)]
Documentation for Team Calendars 3.2 and earlier.
See the [Latest Team Calendars documentation].
25 September 2012
The Atlassian Team Calendars team is pleased to announce the release of Team Calendars 2.5. This release was mostly focused on improving the the initial experience for creating and embedding calendars for admins and first-time users.Previously, once an admin installed Team Calendars we provided no guidance as to what to do next. They'd had to have known to go to the "My Calendars" screen by stumbling across it on the Dashboard or reading our docs. We've improved this experience significantly in this release. If your site has the latest version of the Universal Plugin Manager you will now get a post-install dialog guiding you as to what you can do next:
So it's all find-and-dandy that admins know the plugin is installed, but what about your end-users? We've been thinking of how we can make it easier for admins to communicate to end-users that new functionality is available. To improve this experience, we made use of the WorkBox notification API to notify all end-users once an admin has licensed Team Calendars on their server.
As you're creating a calendar from a page, we've reduced some more friction by automatically linking the calendar current space you are in:
So you've created your first calendar in the editor. Prior to this release, the macro placeholder for the calendar would have looked like this:
We've improved this experience, rendering visual placeholder image symbolising the view you've selected (thanks, Valter Fatia):
|
|
|
In addition, we've also improved the editor property panel states so we have the "selected" state persisted when you toggle different views in the editor property panel.
So we've shown you how it's now easier to discover that Team Calendars is installed in your server, reduced the friction for creating a calendar and improved the visual experience once you've embedded a calendar on a page. We've got a bit further with this experience for first-time users: If this is the first time you're embedding a calendar on a page we now provide a guided tip to help you work out "what next?". From here, users are informed they can continue to modify the macro and save the page to start creating events.
Upgrading from a previous version of Team Calendars is straightforward. We recommend that you back up your Confluence database (which includes Team Calendars data) before upgrading.
Thank you for all your issues and votes. Keep logging issues to help us keep improving!