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

As an admin, I want to more easily find attendees with incomplete registrations #3226

Open
shirgoldbird opened this issue Jun 12, 2018 · 2 comments

Comments

@shirgoldbird
Copy link

Basic idea: If no new or complete records are found in a user's search, instead of just saying "No matches found", update the pop-up to say something like "No matches found. Try searching across all badge statuses" with a link to perform the search.

image

Super-cool stretch goal: in the search results call, check if there are any invalid badges that match the user's search. If there are, display a pop-up with something like "There are incomplete badge records that match your search. Reload and show?".

@binary1230
Copy link
Contributor

Semi-related, in a UX way, to #3065

It's not obvious to reg staffers that they need to take action when encountering a watched attendee, and I saw at least one case where they edited a watched attendee to allow checkin without action and left a note saying 'not sure why it didn't let me check in this person, I changed their status and now it lets me check them in'

@kitsuta
Copy link
Member

kitsuta commented Jun 12, 2018

Yes, that's why we disabled changing badge statuses at-con.

It's tempting to say "it's a training issue" on the one hand but on the other hand, we try to avoid NEEDING training. It's iffy when it comes to watchlist stuff because the conceit is/was that we don't want volunteers stumbling around futzing with the watchlist (like... y'know... changing the badge status so they can check people in), so that's still a little up in the air,

In the case of this issue, though, it's pretty straightforward. We just need to filter invalid badges out after the SQL query instead of before.

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

No branches or pull requests

3 participants