Add Event Type Filtering by Attributes for Better Organization

[angus0817]

Is your proposal related to a problem?

Currently, Cal.com provides many useful attributes when setting up an event type, such as Event Duration, Assigned Host, Location, Scheduling Type, and Event Type Color. However, when browsing through event types, there is no way to filter or sort events using these attributes.

For teams managing a large number of event types, manually searching through the list can be time-consuming and inefficient. A filtering system would allow users to quickly find relevant event types based on specific criteria, improving overall usability and workflow efficiency.

Describe the solution you'd like

We propose adding filters that allow users to search for event types based on their attributes. This would help teams better manage and navigate event types by narrowing down results based on predefined filters.

Some possible filtering options:

• Event Host:
  • Includes Person A (Shows all events where Person A is a host)
  • Excludes Person B (Hides all events where Person B is a host)
• Event Duration:
  • 30 minutes, 60 minutes, custom durations
• Location Type:
  • In-person, Zoom, Google Meet, Phone Call, Custom URL
• Scheduling Type:
  • Round Robin, Collective, One-on-One
• Event Type Color:
  • Red, Blue, Green, etc. (Useful for color-coded categorization)

This would allow users to quickly refine their search instead of scrolling through a long list or relying solely on event names.

Describe alternatives you've considered

Currently, the only option is to manually search for event types by name using the search bar. However, this is not efficient for larger teams with many similar event types or when needing to find events based on specific criteria, such as assigned host or duration.

Additional context

This feature would significantly benefit teams with extensive event type lists, allowing them to organize and locate event types faster, leading to improved workflow management.

Requirement/Document

No external documentation, but this could be implemented similarly to existing filtering features found in project management tools or scheduling platforms.

Example Mockup:

---

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.
  • Follow Best Practices lined out in our Contributor Docs