Skip to content

Preserve unknown properties and components when duplicating events #8605

Closed

Description

@odzhychko

Is your feature request related to a problem? Please describe.

Events can be duplicated.

Image

When duplicating an event, only a selected set of properties and subcomponents are duplicated.

Through #8522 apps will be able to extend the event creation and potentially use new properties and components that we currently discard during duplication.

In general, this is also useful when events are managed through third-party clients that also might support additional properties and components.

Describe the solution you'd like

Copy over all properties and subcomponents.

Describe alternatives you've considered

No response

Additional context

No response

Activity

  1. self-assigned this
    on Jul 16, 2026
  2. added
    1. to developAccepted and waiting to be taken care of
    and removed
    0. to triagePending approval or rejection
    on Jul 16, 2026
  3. added and removed
    1. to developAccepted and waiting to be taken care of
    on Jul 16, 2026
  4. odzhychko commented on Jul 16, 2026

    @odzhychko
    ContributorAuthor

    @ChristophWurst Last time we talked, we concluded to only copy over the VALARM subcomponent because we could not think of any other.

    In the meantime I found about the subcomponents PARTICIPANT, VLOCATION, VRESOURCE through https://www.ical4j.org/components/#subcomponents and propose to copy over all subcomponents. This would also be consistent for how we copy over subcomponents for recurrences.

  5. changed the title [-]Preserve unknown properties and component when duplicating events[/-] [+]Preserve unknown properties and components when duplicating events[/+] on Jul 16, 2026
  6. added a commit that references this issue on Jul 16, 2026
    edd5110
  7. added a commit that references this issue on Jul 16, 2026
    428550c
  8. added a commit that references this issue on Jul 16, 2026
    cd83847
  9. added 2 commits that reference this issue on Jul 16, 2026
    5677e72
    ec41642
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions