Skip to content

Support: conversation merge and split #45

Description

@Andreas-Froyland

Deferred from Stage 05a on 2026-08-30. See stage-05-decisions.md backlog.

A real need — customers do email twice about the same thing — but not before there is volume to merge. Original spec:

Merge: move all messages from source to target ordered by createdAt, move participants and tags, close the source with an activity message linking to the target, keep the source resolvable by displayId.

Split: move a selected message and everything after it into a new conversation, with activity messages on both sides.

Risk: merge moves rows across conversations. One transaction, and the source is retained rather than deleted — two conversations sharing history is very hard to unwind after the fact.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions