Index
[Downloads (PDF, HTML & XML formats)]
Documentation for Team Calendars 3.2 and earlier.
See the [Latest Team Calendars documentation].
2013 年 2 月 18 日
The Atlassian Team Calendars team is pleased to announce the release of Team Calendars 3.1. This release was mostly focused on making Team Calendars align with the new Atlassian styles, small improvements and support for the upcoming Confluence 5.0 release.The release makes the most of the new Atlassian Design Guidelines about to be introduced in Confluence 5.0. This release is backwards compatible with previous versions of Confluence, however the new design improvements will not appear until you have upgraded to Confluence 5.0. Team Calendars 3.1 will get the Team Calendars visual refresh:
We've improved the integration with JIRA project calendars so it's even easier to quickly identify completed issues or releases. Issues and versions which are resolved now appear with a different visual styling in Month, Week and Timeline views. This is particularly helpful for IT teams with lots of scheduled deployments, environment bookings and outages. You can quickly identify if the scheduled task was completed:
Previously, accessing the Calendars in Confluence would be through your username menu. For OnDemand customers, this was only accessible from the Confluence dashboard. As of Team Calendars 3.1 (and Confluence 5.0), calendars are easily accessible from the Confluence header:
In Team Calendars 3.0, we introduced a new Timeline View to help you visualise your team availability, company events and your JIRA project releases. We've made a few interaction improvements to this based on your feedback:
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.
You can view a list of all the issues resolved here. Thank you for all your issues and votes. Keep logging issues to help us keep improving!