nus-se-bot
commented
7 months ago Team's Response
We would assume a fast typist would be accurate at typing, and not be making many typos. In addition, this is intentional to ensure that affiliations can be specifically tied to an existing individual; allowing for non-exact inputs would defeat the purpose of the command, as it would cause bugs from forming wrong affiliations with people. A solution could be to use indices instead of names, which is a potential implementation in the future.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Choice of usage of names as a/ parameter
To add affiliations, users must use the names of the affiliation. This might be inconvenient or difficult especially if the person in the contact list has a very long name.
Copy and pasting is not allowed in the app either.
[original: nus-cs2103-AY2324S1/pe-interim#3763] [original labels: severity.Low type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Hi tester. The use of such long names can be considered extreme user behavior. However, we cannot deny that some typing is needed in writing full names. We can potentially implement functionalities to take in indices in the future.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [x] I disagree
Reason for disagreement: The original bug deals with the issue of long names for adding affiliation.
This issue deals with case sensitivity for adding affiliations.
Since one can be fixed independently of the other, they are not duplicates (as per the module website).
Prof has also justified this in the forum that this should not be duplicates as fixing one does not automatically fix the other.
Moreover, your team decided to mark this as a duplicate without any justification.
## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
The a/ needs to type in the name , forcing the user to scroll and find the name . the input also needs to be exact and full name is needed with case sensitive . -very not great for fast typist and defeats the purpose of a CLI if we need to scroll to find the person's full name
cannot even copy paste the name from the display box