D
Demetrius
We frequently use the “Clone Event” feature as a template for building new events, which is very helpful. However, cloned events are automatically published, creating workflow issues.
When an event is cloned, it is immediately published before edits are made. This can:
  1. Trigger notifications to subscribers about an unfinished event
  2. Send a “your event is ready” email to our internal events inbox
  3. Surface incomplete details publicly before updates are finalized
At the cloning stage, we’ve only duplicated a template - dates, times, ticket types, and logistics have not yet been reviewed or updated. Automatic publication increases the risk of confusion and premature communication.
Requested Enhancement:
Cloned events should default to Draft status rather than automatically publishing.
Alternatively, include a prompt at cloning:
-Clone as Draft (recommended default)
-Clone & Publish
This would give organizers full control over when an event becomes public and when notifications are triggered.
Thank you!