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

Feature Request: Search by Custom Questions #882

Closed
jberkus opened this issue Feb 19, 2020 · 5 comments
Closed

Feature Request: Search by Custom Questions #882

jberkus opened this issue Feb 19, 2020 · 5 comments
Labels

Comments

@jberkus
Copy link

@jberkus jberkus commented Feb 19, 2020

Problem you are facing

Currently, you cannot search, sort, or filter by custom questions, either for speakers or for submissions. Since these custom questions are frequently more important to the organization than the built-in questions, this is an obstacle to using Pretalx for many events. Right now, the only way to do this is to pull data exports and use an external program.

Possible Solution

Add a custom-question drop down, with "question" and "value" to the search interfaces for both submissions and speakers. Ideally, this would be part of an "add criteria" interface, where you could add several different criteria. But even allowing filtering by one custom question would be helpful.

Context

Some examples:

For selecting talks for an upcoming event, we require a higher rating for submissions where the speaker requires travel funding. However, we have no way to filter our list to either those that do or don't need travel funding so that we can select talks this way. Once we've selected the talks, we'll also want to extract a list of speakers who need travel funds so that we can have accounting contact them.

Many conferences need to check how they are doing on selection of under-represented minority speakers. For this, they'd want to filter a list of speakers with the URM-related custom questions to see if they've picked enough.

@rixx
Copy link
Member

@rixx rixx commented Feb 19, 2020

Absolutely agreed, that would be a nice feature to have. It's rather big in scope, so I can't say when it will be implemented – our roadmap for non-sponsored features for 2020 is pretty much set already, but perhaps somebody will want to pick this issue up – I'll be happy to advise in that case!

@rixx rixx added help wanted issue:feature issue:ux 🎀 size:regular 🐐 stage:up for grabs 📤 labels Feb 19, 2020
@eriktews
Copy link

@eriktews eriktews commented Apr 11, 2020

Hi, that sounds like a great idea and it would be cool to see it for the Email composer as well. For example you might have a custom box "would like to attend the conference dinner", and when there are changes to the conference dinner, you could then send emails to everyone who had this box checked. This is pretty similar to #715 so maybe we could have advanced search filters and once we have a result set we like, we could have a button that drops us right into the email composer to mail all speakers that are in our results.

@rixx
Copy link
Member

@rixx rixx commented Apr 14, 2020

Linking between search filters and email adressees would be extremely good UI, thank you for the suggestion! I'll try to push the changes in email handling forward soon, and after that it'll be easier for new/old/any contributors to take up ideas like this.

@eriktews
Copy link

@eriktews eriktews commented Apr 14, 2020

Great, and the existing selectors for the email composer could then become persistent search filters. Maybe you could add a feature that allows you to persist a custom search, such as "all vegetarians" and then have it visible in the email composer as well.

@rixx
Copy link
Member

@rixx rixx commented Jul 28, 2020

You can now go to a list of submissions with a specific answer from the question statistics page, by following the link in the line of the statistics table you're looking at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants