I think the key here is that the questions should be available per ticket, and the ticket type should determine which questions are asked. The new "custom questions" feature is great but does not address the need here for things like selecting a meal preference or t-shirt size for each ticket sold.

We are seeking volunteers to trial our new custom questions model in exchange for feedback about it. This highly requested enhancement to the second-generation payment form will allow nonprofits to add custom questions to the donation checkout process, save custom questions in a Custom Question Library for reuse with other fundraising pages and export a Question Report CSV of custom questions and donors’ responses. Want to join? Learn more about the custom questions beta program: https://www.givelively.org/updates/give-lively-seeks-nonprofit-participants-for-custom-question-beta-program

I would echo this. I am coordinating an event where I need parents to register their young children. I can't change labels on the First Name and Last Name field to indicate a preference for child's name, and I can't add more than one additional question. It would be nice to have additional question options, but also to have questions for each ticket, such as the name of the child belonging to each registration. As it stands, I must clutter registration item names with extra text about registering only one child at a time, and I can't restrict the purchaser from selecting 3 registrations for all kids at one time, plus when they get to the registration information screen, I can't specify which name should be entered, etc. Ticket level questions would solve this issue.

Just want to revisit and re-emphasize this a year later. All of our large events always have at least two additional questions: Meal Choice and Table Captain. Both are generally a "pick one from a list" (aka dropdown) choice. This is literally the only thing that is forcing us to use another solution for event ticketing.

While a full form builder would be nice, it's probably overkill. Just having the option of have more than one custom question and their field type be a dropdown/listbox would serve the vast majority of our use cases.

Custom would be nice.