Improve discoverability and handling of calendar entry attachments in Modern UI
Current behavior
In the Modern Web Client, importing calendar data such as .ics files is available under:
Settings → Accounts → Import/Export
This functionality is therefore primarily exposed as an account-level import operation.
Problem
Importing calendar entries is conceptually a Calendar operation, not an account-management task. Placing the functionality under Accounts makes it difficult to discover.
The problem is particularly apparent when calendar/event data is received as an email attachment. If Zimbra can recognize an attachment as containing a supported calendar entry, the user's intention is usually very clear: add that event to their calendar.
Requiring users to navigate to account settings—or otherwise making the import functionality difficult to find—does not match this workflow.
It can also give users the impression that the Modern UI does not support importing calendar entries at all.
Suggested improvement: contextual attachment action
Whenever Zimbra recognizes an email attachment as supported calendar/event data, expose an action directly in the attachment bar, for example:
Add to Calendar / Import to Calendar
The functionality should be based on whether Zimbra recognizes the attachment as supported calendar data rather than unnecessarily depending only on a particular filename extension. .ics / iCalendar files would be the primary use case.
Selecting the action could open a small dialog allowing the user to select the target calendar before importing the event.
This would provide a simple workflow:
Receive calendar entry by email → Add to Calendar → Select target calendar
Additional Calendar entry point
The same import functionality could also be exposed directly from the Calendar UI, for example through:
Calendar menu → Import calendar/event
Right-click on a calendar → Import calendar file
The existing Settings → Accounts → Import/Export functionality could remain available for bulk imports and other account-level import/export operations.
Documentation
The Modern Web Client documentation should also clearly document this functionality.
At minimum, it should describe:
which calendar/event attachment formats are supported,
the existing import path under Settings → Accounts → Import/Export,
how calendar entry attachments received by email can be imported,
how the proposed contextual Add to Calendar / Import to Calendar action works,
and where users can find calendar import functionality within the Modern UI.
The documentation should preferably describe this as importing calendar events/calendar data, rather than presenting it purely as an “ICS import” feature, while identifying iCalendar/.ics as the common supported format.
Expected benefit
This would:
make calendar import substantially easier to discover,
support the natural email-to-calendar workflow,
avoid unnecessary navigation through account settings,
align the functionality with the user's mental model,
and reduce the perceived feature gap between Classic and Modern UI.
The core interaction becomes:
Calendar attachment received → Add to Calendar
rather than requiring the user to know that a calendar-related function is located under account settings.