search

wang-xinrong / pe

0 stars 0 forks source link

Identifying student contacts using NUSSET ID is troublesome and slow #8

Open wang-xinrong opened 6 months ago

wang-xinrong commented 6 months ago

Identifying student contacts using NUSSET ID is troublesome and slow.

Currently commands mark, unmark and delstu all locates student entry using their NUSSET ID. The UG even suggested the workflow of "find Betsy" to find out NUSSET ID of Betsy before keying it into the command box to delete her contact.

image.png

However, the GUI does not support copying NUSSET from the search result, and the user really have to manually key the 7 digits long NUSSET ID. This make the product less convenient to use to the TA.

However, given the TA probably only need to delete their students contacts a few times a semester, the severity of this feature flaw is low.

soc-se-bot commented 6 months ago

Team's Response

I am not entirely sure what you are referring to by NUSSET ID.

user really have to manually key the 7 digits long NUSSET ID.

I am assuming you are talking about NUSNet ID, we have autocomplete feature to ease typing of NUSNet ID. The user can scroll through all possible options using TAB scrolling, given an NUSNet ID to autocomplete, as stated in our user guide:

image.png

Hence, we disagree that using NUSNet ID is "troublesome and slow".

Furthermore, we believe that your suggestion of copying the NUSNet ID is a less efficient workflow, compared to autocompleting the result. This is because a user has to move their mouse to the text to copy, and then return to their keyboard when copying (Ctrl + c), move their mouse back to the command input box, and then paste (Ctrl + v). Autocomplete does not disrupt the user's typing workflow, as the user is still focused in the command input box.

Therefore, this issue is rejected.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Apologies for the typo, I was indeed referring to NUSNET ID.

NUSNET ID consists of 7 digits and 2 letters, the likelihood of the user choose the wrong autocompletion result is rather high given the size of the command box (autocompletion is implemented without a dropdown list but instead is just a word suggestion).

The dev team could always have implemented arrow key navigation of the contact lists and a shortcut to copy the NUSNET ID. Given the team's decision to focus on using NUSNET ID as the contact identifier, such a feature could have greatly improved user experience.

Thus I disagree with the dev team's rejection