Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import feature's errors too vague #1

Open
estellelim opened this issue Nov 15, 2024 · 1 comment
Open

Import feature's errors too vague #1

estellelim opened this issue Nov 15, 2024 · 1 comment

Comments

@estellelim
Copy link
Owner

estellelim commented Nov 15, 2024

Since the point of having an import function is most likely to hasten up the process of adding a large number of students, if the error message is this vague, it will actually cause the user to spend more time trying to figure out what went wrong. If its a field that's not valid (like unaccepted character in name), the user will have to go through a list of let's say 50 people and check every single field, which is not very ideal.

image.png

@nus-se-script
Copy link

nus-se-script commented Nov 18, 2024

Team's Response

Accepted as error messages do cover the bounds of both invalid or missing data with the same message thus can be considered 'vague'. However, based on the notes this should be at most severity low not medium thus it has been moved down.

Items for the Tester to Verify

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

  • I disagree

Reason for disagreement: [replace this with your explanation]


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants