Managed Event doesn't yet support a Hidden Event toggle in parent event

[alishaz-polymath]

Currently, a managed event doesn't have hidden event toggle for parent events. Each child event can mark as hidden but that can not be done at parent level (default). We should add the ability for admins to control it at parent level, and even lock/unlock it.

[linear]

CAL-6920

[Coderhirdesh07]

I want to work on this issue can you help me to understand it better.

[alishaz-polymath]

Sure thing, feel free to work on it and open a PR. It's essentially the toggle that exists for all event types which allows you to hide an event type (so the event type doesn't show up on the profile page). See below, the toggle:

We don't have this for managed events. Once this is added to parent managed event, this should propagate to the assigned child events (as other properties from the parent managed event does). This should also allow locking/unlocking functionality like the other fields.

[Priyaanshuuu]

Hey I want to work on this issue, can I??
So lemme explain how much I understood what the real issue is, please correct me if I'm wrong. So the real issue is that the some hide button is missing for a specific user or a group of users along with the usage of hiding the data, right is this the issue??

[Tanushree-122]

Hi 👋
I’d like to work on this issue.
Before starting, could you please confirm:

1. Where the parent/child event relationship is defined (model or API)?
2. Whether hiding a parent event should automatically hide all child events?
3. Is there any existing permission or feature flag logic to reuse?

Thanks!

[harshentau-spec]

Hi @alishaz-polymath and team,

New contributor here. I'd like to work on adding the hidden event toggle for parent managed events.

Answers to @Tanushree-122's questions:

1. Parent/child relationship is defined in the database models (likely ManagedEvent and EventType tables with foreign keys) and API endpoints for managed events.
2. Yes, hiding the parent should automatically hide all child events (propagate like other parent properties).
3. Reuse existing permission logic from other fields (e.g., the lock icon functionality in event type forms) and feature flags if any for enterprise.

Plan:

• Add "Hidden" toggle in parent managed event form (UI component reuse from regular event types).
• On save, propagate to child events via backend (update query or hook).
• Add lock/unlock for the toggle.
• Test propagation and visibility on profile page.

Can I proceed? Thanks! 🚀

[ame2en]

Hey I want to work on this issue, can I??