Feature - QR codes/ticket system #537
Conversation
IGORnvk
added
feature
|
Everything that was listed works, but I'll wait up on the changes we spoke about before confirming. |
…onference into feature/qr-codes
|
Ready for review ✅ |
|
I am mighty impressed by this haha. Very good job Ihor! This is basically what I wanted since we started the conference. |
There was a problem hiding this comment.
Minor text issues persist. I'll approve it so that it still can make production.
One question I have is, can we make it so the ticket gets send a week or so before the actual conference? I am worried that the ticket otherwise will get lost in the endless emails that some company members receive daily etc.
This sounds like a Scheduler stuff, but we can make it so that ticket is sent as soon as the programme gets released. |
That's sounds like a better idea if you ask me |
Okay then, I will do it today |
|
@v-stamenova @TimKardol I have added the command to create tickets for existing verified users. You can test it out. Also now you are receiving the mail with your ticket once programme gets released. I suggest to test everything in the list again just to make sure it works well. |
So to verify the flow no longer starts like this:
Now I should start with programme release? |
"After that, you should log in as an event organizer and publish the programme. After you published:" So, to answer your question, yes. :) |
Description
Introduces ticket functionality through QR codes. It requires user to verify their email after registration on our website.
Type of change
What needs to be tested
Prerequisites:
email_verified_at' => now(),inUserFactory)After that:
app/Actions/Fortify/CreateNewUser.php).After that, you should log in as an event organizer and publish the programme. After you published:
/moderator/ticketsand make sure that the scanner is displayed (for that you might want to modify the condition intickets->index.blade.phpcause there is no way to make edition in progress rightaway).moderator/usersand verify that ticket was scanned successfully.moderator/tickets. It should throw 403.Additionally:
moderator/userspage test the filter dropdown after you scanned some tickets and verify that the system puts first the users who have their tickets scanned.moderator/ticketspage test responsiveness of the scanner. On mobile screens there is a button to activate scanning.Checklist: