-
Suggestion
-
Resolution: Unresolved
-
None
-
113
-
4
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Although this is similar to TEAMCAL-269, this is more focused on the reporting use case.
We've had requests for the ability to get calendar information for reporting purposes. This is a slightly different set of API requirements than the ability to create, edit and update calendar events.
This issue is to track the general requirements to:
- Get a listing (or sub-set) of calendars based on some query
- Get some calendar metadata
- Creator
- Last updated
- # of events
- etc...
Dear customers,
Thanks for all of your continued interest for this suggestion.
Unfortunately, we’re unable to yet place this suggestion on our roadmap. We acknowledge and understand the value a robust calendar API would bring, and and will continue to monitor customer interest in this space.
The implementation of this feature aside, we wish you to note that via Team Calendars we include the CalDAV protocol. This not only gives customers the ability to use Team Calendars in your favourite calendar app, but it also provides its own standardised API for calendar event retrieval and manipulation. We’ve recently built out documentation showing how to use this protocol on developer.atlassian.com and hope that you'll find it useful as a workaround for the time being.
Cheers,
Michael Andreacchio
Confluence DC Product Management
- duplicates
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
- relates to
-
- Gathering Interest
-
- Future Consideration
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Would be very useful as a simple sprint availability forecast!
+10000 teams 
We use wiki calendars for easy input and shared visibility of vacation tracking. We would like to be able to pull this data into allocation vs. workload reporting.
e.g. Members of Team X are expected to spend 50% of their weekly sprint time working on tickets. Standard weekly allocation is 40h*0.5=20h per user. If Bob is ooo for 2 days during a sprint, his expected allocation drops to (40h-16h)*0.5=12h. Bob logged a total of 22h against tickets during this sprint. Bob is either neglecting the other 50% of his accountabilities OR Bob just needs to chill and stop working overtime.
Either way, the point is we need to be able to poll vacation data to complete the calculation.
Dear customers,
Thanks for all of your continued interest for this suggestion.
Unfortunately, we’re unable to yet place this suggestion on our roadmap. We acknowledge and understand the value a robust calendar API would bring, and and will continue to monitor customer interest in this space.
The implementation of this feature aside, we wish you to note that via Team Calendars we include the CalDAV protocol. This not only gives customers the ability to use Team Calendars in your favourite calendar app, but it also provides its own standardised API for calendar event retrieval and manipulation. We’ve recently built out documentation showing how to use this protocol on developer.atlassian.com and hope that you'll find it useful as a workaround for the time being.
Cheers,
Michael Andreacchio
Confluence DC Product Management