-
Notifications
You must be signed in to change notification settings - Fork 563
Students can easily link to wrong identifier, can't unlink #2542
Comments
If you could help me unlink that would be great, the github account that doesn't know which identifier is linked to is ilica. I can't search the roster for that from what I can see, so it would be great if you could do that. |
@amueller This is an interesting edge case we hadn't thought of, thanks for letting us know! We'll see what we can do here. The identifier your student matched to was |
This edgecase happened about 5 times in my class of 225 students ;) I think the most important take-away is to make the sign-up a two-click process instead of a one-click process. |
It's happening more and more times, and together with the students not being able to figure out which identifier they are linked to, it's pretty tricky to fix, as I can't search for their github user accounts in the interface. |
I also see this often. I raised it last year in #2455. Once a student does this it means that the real owner of the identifier can't select it, compounding the problem. I then have to use the awful roster management interface to try to detangle the associations. |
Posting here as well for folks discovering this issue, we've shipped a small improvement to this interface, it now asks students to verify they clicked the correct roster entry before continuing. Thank you both for your feedback, we really appreciate it. We're working on a new system some time soon! |
Feature request ✨
From my students experience, it looks like it's very easy to link an account to the wrong identifier. I assume a single click is enough. It would be better if this would require also clicking "ok" or similar.
I had several students link to the wrong UNI.
Once they link to the wrong identifier, they can't unlink.
I had students link to random identifiers that they accidentally clicked on, and now I do not know how to find them in the roster and unlink them.
The text was updated successfully, but these errors were encountered: