Team Calendars 4.0リリースノート
2013 年 8 月 21 日The Atlassian Team Calendars team is pleased to announce the release of Team Calendars 4.0. This release was focused the simplification of creating calendars and events.
- Below is a list of highlights for this release
- Also see our complete list of issues resolved.
Prior to 4.0, Team Calendars shipped with a JIRA calendar (to plan JIRA releases and projects), a People calendar (leave/travel/rosters...) and an Event calendar (for team events). While the concept of calendar types was very helpful to in communicating how this add-on is different to your personal calendar, it created a lot of friction. A team lead would need to:
1. Create a calendar for their JIRA projects
2. Create a calendar for their leave/travel
3. Create a third calendar for their events or to track simple things like a public holiday, training or social events
After creating their calendars they would then:
4. Share each calendar (one at a time) with their team members
5. Each team member would then subscribe or watch each calendar in their Confluence calendars view or from their favorite calendar app (e.g. Google Calendar, Outlook etc..)
6. If they wanted to embed them in content, like their team homepage, they (again) would need to do this three times.
The concept of calendar types introduced a lot of admin overhead.
Goodbye Calendar Types, Hello Event Types
Team Calendars 4.0 removes the administration overhead when having to maintain, subscribe, watch and share several or more calendars with your team. We've done this by combining them into a single calendar and enabling a user to classify events by type.
One calendar to rule them all
Teams can now create one calendar for their team and embed it with different types of events:
What happens with my existing calendars? There should be no major change in terms of having to re-subscribe etc.. The main improvement here is that you can go to any existing calendar prior to 4.0 and should be able to add any type of event to that calendar - regardless of it's original "type".
What if I work in multiple teams? Not a problem, you can still subscribe to multiple team calendars if you need to, we haven't taken this away.
What happens if I export a calendar? You can export and import calendars with different event types and all the data will be stored.
See all events together in one calendar, or show and hide events to focus on some
A Team Calendar is great to communicate and visualize your teams availability (leave, travel...), events and JIRA projects. Doing so can help you see how your teams availability could impact your project. But sometimes you want to focus on a particular type of event. In Team Calendars 4.0, you can show and hide events by type:
Simplified adding of JIRA project events
Previously, we had one JIRA calendar dialog where in which you could embed JIRA project releases (versions), JIRA Agile Sprints or Issue due date and durations. Although this is quite powerful, it's also complex to get started.
To make this easier, we've created specific event types for JIRA releases and JIRA Agile sprints. To embed a stream of JIRA releases or Agile sprints, all you have to do now is select the project and that's it!
Confluence 4.2 Required
Team Calendars 4.0 requires Confluence 4.2 or higher. Learn more about the Team Calendars Support Matrix
Upgrading to Team Calendars 4.0
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.
- In Confluence, simply click 'Upgrade' in the Team Calendars entry of the Plugin Administration screen.
Alternatively, download the latest release from our plugin exchange and install it via the Plugin Administration screen. This should upgrade Team Calendars to 4.0.0 (or higher).
If you run into any issues, to down-grade simply install an the previous version of Team Calendars you were running (also available from the marketplace).
Issues Resolved in this Release
Thank you for all your issues and votes. Keep logging issues to help us keep improving!