Cloned Events Should Default to Draft Status
complete
W
WFAE
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:
- Trigger notifications to subscribers about an unfinished event
- Send a “your event is ready” email to our internal events inbox
- 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!
Log In
Michel (Product @Zeffy)
This is now live! 🎉 When you clone an event, it now starts in Draft status instead of being published immediately. This gives you time to review and adjust the details before it goes live.
C
Christine
Michel (Product @Zeffy) Thank you.
Michel (Product @Zeffy)
marked this post as
complete
M
Michelle Lee
Michel (Product @Zeffy) Thank you!! You guys are amazing! 💜 Is there also a way to return a published event/campaign, etc., to draft status?
B
Brickomanie
May I add to this request that we should be able to go back to draft status for any published campaign? I can't have everything always public.
W
WFAE
Brickomanie Agreed! It'd definitely be great to change back to draft status!