Index
[Downloads (PDF, HTML & XML formats)]
Documentation for Team Calendars 3.2 and earlier.
See the [Latest Team Calendars documentation].
This page covers basic instructions for adding JIRA calendars to Confluence.
JIRA calendars enable you to visualise any issue date and project due dates from JIRA. To use this feature, you must have your Confluence and JIRA instances set up with a secure connection between them. See Licensing and Installing Team Calendars.
On this page:
To add a JIRA calendar, click 'Add Calendar' > 'New Calendar' > 'JIRA Calendar'.
When creating a JIRA calendar, you will be presented with a few options:
If selecting "Saved filter" or "JQL", Team Calendars will render all the available date fields that are available for all projects selected in your filter. If there are dates that are only available to one project, and not another in the filter, they will not render in the list of possible fields to show.
Upon selecting a Project, Saved Filter or JQL, you will be presented with all the possible dates that can be rendered in Team Calendars. For those of you with GreenHopper, Team Calendars can also embed your GreenHopper sprint durations right on your JIRA Calendars.
Once the calendar is created, depending on what you've selected, you could see:
Some samples:
You cannot add content to JIRA calendars here. They source all of their date information from the JIRA system. To add issues and version deadlines, add them in the JIRA interface.
Tip: You can drag-and-drop your JIRA issue dates and project versions to re-schedule them right from Team Calendars.
Note: Upon creating a JIRA calendar, all users in your system can see the calendar name in Confluence. However, the contents of the actual calendar events (issues, versions, sprints etc...) automatically respects your JIRA permissions - so it is possible for users to be subscribed to a JIRA calendar and not see all events. This is controlled by your JIRA permissions.
Subscribe to and from Team Calendars from other calendars.