Deleting tickets sets the 'Total Capacity' to 0 about events

[engram-design]

The only way I'm seeing this, is if the "Total Capacity" is empty, and you delete all the tickets. The capacity will be set to 0.

The capacity of an event should be independent of the ticket quantities. The only case where it will populate the total capacity is if that's empty. For example, you skip setting the capacity, and create your tickets with the quantity. It'd be useless to have an event with 0 capacity, while having tickets available for purchase - but you can't buy any with a 0 capacity.

Is this the behaviour that is an issue for you?

[anchovy]

Yep / that's what's happening. I can see instances where an admin creates/edits an event and adds a ticket, realises its the wrong ticket type and rather than change the ticket type deletes the ticket and adds a new one - not realising that the total capacity has been automagically set to 0.

Also, in our case, we have a ticket type that will never have a max capacity so we'll never want a max capacity of 0.

I could understand if the default capacity was 0 and there was a toggle for enforcing max capacity, but there isn't, so this value shouldn't be arbitrary set when all tickets have been deleted. Also,the notes say something like this is limit is independent of the individual ticket quantities, so again shouldn't be set based on a ticked change/deletion.

(Sorry for the rambling notes!)

[engram-design]

Fair enough, I'll give this some thought. I just wanted to check as I couldn't replicate it with a value set in the total capacity field, when adding or deleting tickets.