Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capture show ticket sales URL/price per performance range? #789

philosophicles opened this issue Jan 6, 2020 · 0 comments

Capture show ticket sales URL/price per performance range? #789

philosophicles opened this issue Jan 6, 2020 · 0 comments


Copy link

@philosophicles philosophicles commented Jan 6, 2020

A show currently has two fields "Ticket URL" and "Ticket prices", collectively labelled "Ticket sales" on the show creation/edit screen. These are captured once for the show as a whole.

At least some of the time when a show has multiple performance ranges, either the URL and/or the price will vary per performance range. For price, this relation is currently expressed in words within the Ticket prices field. E.g. different prices for matinees vs evenings; different booking URLs for performances in different venues (esp. for tour shows).

Perhaps, from a database perspective, these fields should become tied to the performance range, rather than the show as a whole? In terms of interface, it might be good to let people choose whether they want to define them globally or per performance range.

Some change would be needed to how such information is presented to non-admins on the main show screen.

Sometimes the price will also vary within a performance range, but a slight redefinition of "performance range" could introduce price as a factor that should prompt creating a separate performance range.

The counter-argument is that this might just get too complicated (in the front-end) to be worth it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.