You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm using the opsgenie .ical feed to import my shifts into my own calendar. This works great, but there is one small issue with this: the feeds only contain data which is a few weeks in the future. I would love to see way more data from the future, so I want the .ical feed to expose the coming 12 months, instead of the coming 4 weeks.
Hi @rogierl ,
It's not possible at this time to export a calendar for the next 12 months. It's only limited to 3 months currently.
"You can also choose to export the schedule periodically. Select Open calendar from the icon bar to export the next 3 months to your calendar, starting from the current month. At the end of the initial 3 months, Opsgenie will automatically keep exporting the next 3 months period from the schedule."
@nick thanks, I indeed use that function to "subscribe" to the opsgenie shifts. However, why is that feed limited to only 3 months? This doesn't really make sense. It would be better to have it expose the coming 12 months. For example, if a team with night-shifts want to plan the summer holidays, then they often have the need to see data > 3 months form now.
What is needed to extend the default time window exposed by the export feature?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately it's not possible to extend the default time window 3mo>
And I'm not entirely sure why it's limited to 3 months either.
But we have an open feature request you can follow here: https://jira.atlassian.com/browse/OPSGENIE-461
I'd recommend voting for the feature request, and adding yourself as a watcher. The more votes / watchers on a feature request, the higher likelihood engineering will consider adding it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.