[wp-meta] [Making WordPress.org] #3493: CampTix: Poor UX when one ticket type is sold out
Making WordPress.org
noreply at wordpress.org
Mon Mar 5 09:46:28 UTC 2018
#3493: CampTix: Poor UX when one ticket type is sold out
---------------------------------+-----------------------------------------
Reporter: hlashbrooke | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: WordCamp Site & | Keywords: needs-patch has-screenshots
Plugins |
---------------------------------+-----------------------------------------
CampTix allows WordCamp organisers to create multiple ticket types. The
most common usage of this is to create the following two tikets:
1. A general admission ticket (no more than the local equivlent of
$20/day).
2. A "micro-sponsor" ticket, which is generally around 3-5x more expensive
than the regular ticket.
This is entirely correct, but the issue comes in when the general
admission tickets are sold out and there are only micro-sponsor tickets
remaining. This happened recently in the case of WordCamp Greenville and
it creates a confusing UX for potential attendees. See these URLs to see
the issue:
* Ticket sales page: https://2018.greenville.wordcamp.org/tickets/
(screenshot attached below because this page will be outdated soon)
* Tickets CPT in the dashboard: https://2018.greenville.wordcamp.org/wp-
admin/edit.php?post_type=tix_ticket (only visible to organisers)
The issue here is that a potential attendee comes to the ticket sales page
and only sees the micro-sponor ticket available, then thinks that the
tickets for the WordCamp are $100 each (this did actually happen, so it's
not a made-up scenario). If we had some kind of indicator that the other
ticket type was sold out, then that could help to mitigate this issue.
I created a quick mockup for a potential solution here (attached below)
that does the following if a ticket type is sold out:
1. Does ''not'' remove the ticket type from the table.
2. Replaces the quantity select box with a 'Sold out' string.
3. Reduces the opacity of the row to `0.3`.
There may be a better solution for this as this was a very quick mockup,
so open to ideas here of course. Essentially I think we need to improve
the UX so that it's clear what tickets are sold out to prevent confusion.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3493>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list