To enable calendar view for your release and version click on “Calendar” in top navigation bar
...
All versions and releases from the board that have Release Date specified will be shown on the Calendar view.
versions are shown Green
release are Blue (thus we are consistent with other view through out the App)
...
Tags to filter by Version/Package tags
Archived/Unarchived
Show delayed only
Columns representing status (or steps in workflow) for versions and releases
Filter by Projects
Filter by Project Leads
FIlter by version specific and release specific Custom Properties
Export
...
By clicking on export to ICS button you can generate a standard calendar.ics to include it into any standard office/calendar app you are using.
...
(.ics snapshot or permanent link)
There are couple of ways to export Release Calendar and share with your stakeholders, namely:
Dashboard Gadget (see the section below)
Import Gadget into Confluence
Export .ics snapshot and import in your calendar tools (like Outlook, Google Calendar, etc..)
Share a permanent link to your real-time calendar with all the filters saved
...
Share Calendar via Permanent Link
As outlined above we generate a permanent link that you can use to share your real time release calendar with your stakeholders via 3rd party tools. The link encodes all the filters you selected and all the updates happening to versions, release and their milestones will be automatically replicated in your 3rd party tool.
Note |
---|
Security considerations: Obviously to access this permanent link / release calendar from 3rd party systems you need to perform authorization. We support Basic and Token (prefered) based authorization. Therefore, your 3rd party tool should be able to provide such. Below we will show 2 examples how to do with Postman and Confluence. |
Example A: Pull Release Calendar via Postman
...
Example A: Upload Release Calendar into Confluence
Please follow the following instructions from Atlassian to create your confluence calendar
Available as Gadget?
Sure, check respective section of this documentation.