Known limitations
What Event Planner doesn't do today, and what to do instead.
| Limitation | What to do instead |
|---|---|
| No recurring events. Each event is a single occurrence. | Add each occurrence, or generate them with Create with AI. |
| No reminders or invitations. People on an event aren't notified. | Export the events to ICS and import them into your calendar app. See Export events. |
| No live sync with Outlook or Google Calendar. Export makes a one-time copy, and Event Planner can't import or subscribe to other calendars. | Export again after the plan changes. |
| No combined view. A calendar shows only its own events. You can't see several calendars, or all work item calendars of a space, in one view. | Use one space calendar for the team, and embed it where people need it. |
| No link to Jira dates. Work item calendars don't show due dates, sprints or versions. | Add key dates as events on the work item's calendar. |
| Events have no owner. Anyone who can edit a calendar can change any event on it. | Limit who can edit, or lock the calendar. |
| No lock on space calendars. | Limit who can edit with restrictions. |
| Event fields are fixed. No custom fields, categories or attachments. | Use colors for categories, and the description or link for the rest. |
| Space calendar events aren't searchable. Confluence search finds a space calendar by its name only. | Give calendars clear names and descriptions. |
| No restore from the trash in Event Planner. | Export a space calendar before you move it to the trash. |
| Page calendars don't become space calendars. | Create a space calendar and add the events again, for example from an ICS export with Create with AI. |
| The calendar's own words are in English. Dates and times follow each person's language and region. | - |
| Cloud only. Event Planner isn't available for Confluence or Jira Data Center. | - |
Related
- FAQ: short answers to common questions.
- Limits: the numbers.
- What's new: what changed recently.