It appears that a recurring event that allows enrollment, tracks enrollment separately for each occurance of the event. Is this by design? I'd think that a recurring event, from an enrollment standpoint, would treat all events in the series as the same, i.e. if you enroll for one instance of the event you get enrolled into all instances and the enrolled count is incremented for all events in the series.

The way it works now acts like separate events that were all duplicated and each is a separate event.

I can see the need for both. i.e. I have a training class that is every Mon, Wed for 3 weeks. Create a recurring event and track enrollment at the series level.

I could also see that you have an event that is a one day training event, and it occurs every Mon, Wed for 3 weeks. But each class is meant to be stand alone. I see this more as one event that you provide a duplication or copy function that looks a lot like the recurring freqency fields.

But it seems like the current funcitonality is a mix of the two. The recurring functionality really acts like a way to duplicate a stand alone event instead of truly acting like a single event that occurs on multiple occasions.

Am I missing something?