Attendee Name & Email for Multiple Tickets – WooTickets

[Schalk Joubert]

Hi Barry,
In response to your reply on the attendee names for tickets in this discussion;
https://tri.be/support/forums/topic/page-title-changes-to-undefined-when-using-browser-back-button/
I can understand that you will be frustrated by now by the ongoing nagging. But please understand that you gave us an reason to anticipate this.
==========================================
https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/3738379-collect-all-attendee-information-for-multiple-tick
”Modern Tribe (Admin, Modern Tribe) responded · Aug 30, 2013
Great idea! We have this on the roadmap for WooCommerce: Tickets.”
==========================================
I do not know the criteria for something which is on the roadmap. However;
1.) It is on the roadmap for nearly six months
2.) It is marked as “PLANNED”
3.) This topic is in the top 5 of votes received.
( the latter I do realise is not a given something will be implemented though )

That said and out there, please rather tell us exactly where we stand. As it is know I am in 2 minds, as I much prefer to stick with Wootickets, and should you be working on this feature, then I am happy to wait.

In conclusion, I guess on of the main issues here is that we can not understand why this is so complicated. I know we can’t do it. But isn’t there a way to develop this as an extension, and sell it separately? even by a third party, but recognised by Modern tribe?

Thank you for your replies, feedback and all.
I do appreciate it.
Regards
Schalk

[Rob]

Hey Schalk. Thanks for the note here; you make a really good point regarding how we can better communicate our planned changes/what exactly the roadmap constitutes. We’ve had a few issues lately with users who – because we’ve agreed at one point that a feature does have a place on the roadmap – are falsely led to believe that this means there’s any sense of timetable or timeline associated with that. This was our failure to communicate properly and I apologize to both you and the other users in this same boat.

To us, getting onto the roadmap means a feature is something that – among the hundreds of requests coming at us from all sides – we see value in, enough to log it in our central ticketing repository and to begin taking exploratory steps towards implementation. I will be completely transparent here and say that’s where this feature sits: we have logged it and are continually noting additional requests as they come through. We see value in it and it is indeed one of the two “priority 1” (top level) tickets we’ve got, given the number of requests we’ve had for it. That said there has been no actual code work done on it, beyond a number of discussions on how it could best be implemented; while I think the argument could certainly be made that this isn’t really what the plugin was designed for to begin with – it’s meant to be a light ticketing service, not a full-fledged event management solution – we also realize how important this is to the community and want to implement it.

That said, if we do implement it, we want to do it right. That means on a codebase that is stable and in a way that can carry over across the different plugins in our ticket framework. This needs to be code that is flexible and can support future codebase changes/tweaks to both the core The Events Calendar and WooCommerce itself.

You raise a really good point on the idea of having it as a third-party plugin. If a user were to design something that worked and were willing to share it, we would – pending a quick code review to make sure it was safe to share with the community – absolutely help promote that so users knew they had a solution until we can find a best course of action. Whether someone were to make it as a free plugin on the dot-org repo or something they sold wouldn’t make any difference on that front.

Out of curiosity: what could we have done to better communicate this to you? Is our use of the term “roadmap” too subjective and not specific enough? While we generally don’t plan out specific features more than a release or two in advance, I can see based on your point here that we made need to be more firm regarding what’s being actively considered/planned and what we’ve literally made progress on and have a timeline to release. I’d welcome your thoughts here so we can make this process smoother – and avoid disappointment – for everyone. Apologies in the interim that we let you down.

[Author]

Posts