Issue Summary

When a Calendar in Confluence is being exported into ICS file, Jira Event Types are being exported as X-EVENT-SERIES.
Importing ICS file with multiple Jira Event Types would only import the first event type, where the rest are omitted.

Steps to Reproduce

1. Install Confluence DC
2. Configure Application Links between the Confluence with another Jira
3. Create a new Calendar in Team Calendar
4. Add multiple Jira Event Types into the calendar, linking to the Jira
5. For testing, the Jira Event Types below are added to the calendar:
   • Jira Issue Dates
   • Jira Agile Sprints
   • Jira Project Releases
6. Export the calendar into ICS file
   • Here's a sample of how the above 3 Jira Event Types will be exported into the ICS format:
     Excerpt of ICS export

     BEGIN:X-EVENT-SERIES
     SUMMARY:My Sample Kanban - Releases
     DESCRIPTION:
     X-CONFLUENCE-SUBCALENDAR-TYPE:jira-project-releases
     URL:jira://4a644012-8ec9-3888-8cb0-eb8677d51f6b?projectKey=MSK&dateFieldN
      ame=versiondue
     END:X-EVENT-SERIES
     BEGIN:X-EVENT-SERIES
     SUMMARY:My Sample Scrumz - Sprints
     DESCRIPTION:
     X-CONFLUENCE-SUBCALENDAR-TYPE:jira-agile-sprint
     URL:jira://4a644012-8ec9-3888-8cb0-eb8677d51f6b?projectKey=MSS&dateFieldN
      ame=sprint
     END:X-EVENT-SERIES
     BEGIN:X-EVENT-SERIES
     SUMMARY:My Sample Projekt - Issues
     DESCRIPTION:
     X-CONFLUENCE-SUBCALENDAR-TYPE:jira
     URL:jira://4a644012-8ec9-3888-8cb0-eb8677d51f6b?projectKey=MSP&dateFieldN
      ame=duedate
     END:X-EVENT-SERIES
     

7. Import the ICS file above back into Confluence

Expected Results

All of the same events from the exporting calendar shows up in the imported calendar.

Actual Results

Only the first Jira Event Type is imported, where the rest are omitted.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available