Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-49097

Custom event types after import becomes default events

XMLWordPrintable

    • 37
    • 34
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Steps to reproduce:

      1. Create a new Calendar.
      2. Create a new Event with a custom Event type.
      3. Export as .ics.
      4. Import to Team Calendars.

      Expected behavior:

      The Event should have the event type that we selected.

      Actual behavior:

      The event type shows just as an event.

            [CONFSERVER-49097] Custom event types after import becomes default events

            James Whitehead added a comment -

            A fix for this issue is available to Server and Data Center customers in Confluence 7.11.0
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            James Whitehead added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.11.0 Upgrade now or check out the Release Notes to see what other issues are resolved.

            Alex K added a comment -

            Hi,

            We have released a fix for this issue in Team Calendars 6.1.7.

            Previously if you exported a team calendar to ICS format, and imported it back into Team Calendars custom event type information would be lost. From Team Calendars 6.1.7, when you import a calendar that was:

            • exported from Team Calendars 6.1.7 or later, the custom event type, icon, and reminders will be imported.
            • exported from Team Calendars 6.0 to 6.1.5, the custom event type will be imported, but the icon and reminders will not.
            • exported from Team Calendars cloud or Team Calendars 5.3.x or earlier, events will be imported as the default event type (without custom event information).

            Regards,
            Alex K (Developer at Atlassian)

            Alex K added a comment - Hi, We have released a fix for this issue in Team Calendars 6.1.7. Previously if you exported a team calendar to ICS format, and imported it back into Team Calendars custom event type information would be lost. From Team Calendars 6.1.7, when you import a calendar that was: exported from Team Calendars 6.1.7 or later, the custom event type, icon, and reminders will be imported. exported from Team Calendars 6.0 to 6.1.5, the custom event type will be imported, but the icon and reminders will not. exported from Team Calendars cloud or Team Calendars 5.3.x or earlier, events will be imported as the default event type (without custom event information). Regards, Alex K (Developer at Atlassian)

            sy Sawyer added a comment -

            dsf sd 

            sy Sawyer added a comment - dsf sd 

            Makisa Appleton added a comment -

            Thank you all for your votes and comments. Please note that this suggestion is in active development.

            Thanks
            Makisa | Senior Product Manager, Confluence Server and Data Center

            Makisa Appleton added a comment - Thank you all for your votes and comments. Please note that this suggestion is in active development. Thanks Makisa | Senior Product Manager, Confluence Server and Data Center

            John Gaida added a comment -

            +1

            John Gaida added a comment - +1

            calvin.dike added a comment -

            5 years now and this is still an issue. Can Atlassian revisit this? 

            calvin.dike added a comment - 5 years now and this is still an issue. Can Atlassian revisit this? 

            Nobuyuki Mukai added a comment -

            I share feedbacks from a customer.
            —

            • This should be treated as a Bug because ics file itself stores CUSTOM-EVENTTYPE-ID or CATEGORIES as data for CUSTOM EVENTTYPE.
            • Changing event types manually is not a feasible workaround. Calendar can have thousands of custom events in production environment.

            Nobuyuki Mukai added a comment - I share feedbacks from a customer. — This should be treated as a Bug because ics file itself stores CUSTOM-EVENTTYPE-ID or CATEGORIES as data for CUSTOM EVENTTYPE. Changing event types manually is not a feasible workaround. Calendar can have thousands of custom events in production environment.

            Jenny (Inactive) added a comment -

            Hi all,

            Thanks for all of your votes and comments on this suggestion.

            Unfortunately, this suggestion isn't currently on our roadmap. We do though understand the value in retaining custom event types during imports, and and will consider this suggestion at a later date.

            For those of you who aren’t aware, in our Team Calendars 5.5 and 6.0 releases we brought a range of new improvements, including a fresh new look and feel, better event frequency options, and CalDAV – the ability to use Team Calendars in your favourite calendar app. For more information on these improvements, see: 5.5 release notes, and 6.0 release notes.

            Best wishes,
            Jenny | Confluence Server Product Manager

            Jenny (Inactive) added a comment - Hi all, Thanks for all of your votes and comments on this suggestion. Unfortunately, this suggestion isn't currently on our roadmap. We do though understand the value in retaining custom event types during imports, and and will consider this suggestion at a later date. For those of you who aren’t aware, in our Team Calendars 5.5 and 6.0 releases we brought a range of new improvements, including a fresh new look and feel, better event frequency options, and CalDAV – the ability to use Team Calendars in your favourite calendar app. For more information on these improvements, see: 5.5 release notes , and 6.0 release notes . Best wishes, Jenny | Confluence Server Product Manager

            Joyce added a comment - - edited

            +1 from Continental

            Issue still persists in Team Cal v.6.0.17

            Joyce added a comment - - edited +1 from Continental Issue still persists in Team Cal v.6.0.17

            Dav1d J0nes added a comment -

            How hard can this be, you just need to modify the import filter to create the categories 

            Dav1d J0nes added a comment - How hard can this be, you just need to modify the import filter to create the categories 

            Mandeep Kaur added a comment -

            Also happening in confluence 6.6.2

            Mandeep Kaur added a comment - Also happening in confluence 6.6.2

            Carl Paradis added a comment -

            Hi, I'm also waiting for a fix to migrate to Confluence calendars.

            Carl Paradis added a comment - Hi, I'm also waiting for a fix to migrate to Confluence calendars.

            Alexander Kuhn added a comment -

            Hi, as this issue prevents as from migrating our calendar to the new confluence it would be very nice if it could be resolved in the near future........

            Alexander Kuhn added a comment - Hi, as this issue prevents as from migrating our calendar to the new confluence it would be very nice if it could be resolved in the near future........

            Pavel Boev added a comment -

            We'll attempt to schedule this ticket fairly soon. Current sprints are full, but the effort to resolve this issue is relatively small, so we'll bump the priority and resolve it at the next opportunity.

            Does "fairly soon" mean 2.5 years ('cause they passed already) or more?

            Come on, how could all the sprints since 2015 be always full that you couldn't squeeze this issue, described as "relatively small"?

            Pavel Boev added a comment - We'll attempt to schedule this ticket fairly soon. Current sprints are full, but the effort to resolve this issue is relatively small, so we'll bump the priority and resolve it at the next opportunity. Does "fairly soon" mean 2.5 years ('cause they passed already) or more? Come on, how could all the sprints since 2015 be always full that you couldn't squeeze this issue, described as "relatively small"?

            Michael Blake added a comment -

            Still an issue with Confluence 5.10.7

            Michael Blake added a comment - Still an issue with Confluence 5.10.7

            Terry Welliver added a comment -

            Still an issue in Cloud.

            Terry Welliver added a comment - Still an issue in Cloud.

            Retmer van Dongen added a comment -

            Still a problem in Confluence 5.9.7

            Retmer van Dongen added a comment - Still a problem in Confluence 5.9.7

            Nicolas Chapart added a comment - - edited

            any udpate on this ticket? I have to migrate loads of team calendars from one instance to a new one and this bug is preventing me to do so.
            thanks

            Nicolas Chapart added a comment - - edited any udpate on this ticket? I have to migrate loads of team calendars from one instance to a new one and this bug is preventing me to do so. thanks

            snorrish (Inactive) added a comment -

            We'll attempt to schedule this ticket fairly soon. Current sprints are full, but the effort to resolve this issue is relatively small, so we'll bump the priority and resolve it at the next opportunity.

            snorrish (Inactive) added a comment - We'll attempt to schedule this ticket fairly soon. Current sprints are full, but the effort to resolve this issue is relatively small, so we'll bump the priority and resolve it at the next opportunity.

            Ryan Mensching added a comment -

            This bug is affecting how we use Team Calendars outside of Confluence. This is critical and may cause us to move away from Team Calendars for solutions if not fixed soon.

            Ryan Mensching added a comment - This bug is affecting how we use Team Calendars outside of Confluence. This is critical and may cause us to move away from Team Calendars for solutions if not fixed soon.

              aknight@atlassian.com Alex K
              wzanchet William Zanchet (Inactive)
              Votes:
              75 Vote for this issue
              Watchers:
              76 Start watching this issue

                Created:
                Updated:
                Resolved: