You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.
To the left of each submission on the Waiting List, there should be a checkbox.
Once someone selects at least one checkbox, we enable the "Send emails" button at the top of the page.
It can be at the same spot as it used to be on the Results tab.
When no checkbox is selected, the button should be disabled and the title of it should say "Please select at least one submission".
After clicking on "Send emails", the admin should be taken to another page where they can provide the number of hours people have to confirm the invitation.
After that, let's redirect them to Invited with a flash message saying that the selected people will be invited.
In contrast to sending invitations from the Invited tab, we don't need to account for bad news emails here.
The process behind sending selected submissions should be super tight so that it won't send emails to people who weren't selected by mistake. I was thinking about an approach where clicking on "Send emails" sends the selected IDs to the server, then on the next page with the input for hours we include those IDs as a hidden field. And when the admin finally submits the final form with the hours, we check if those IDs are actually on the waiting list. If not, then let's display an appropriate error message.
The process behind sending selected submissions should be super tight so that it won't send emails to people who weren't selected by mistake. I was thinking about an approach where clicking on "Send emails" sends the selected IDs to the server, then on the next page with the input for hours we include those IDs as a hidden field. And when the admin finally submits the final form with the hours, we check if those IDs are actually on the waiting list. If not, then let's display an appropriate error message.
We should probably finish #153 first.
The text was updated successfully, but these errors were encountered: