search

albertsutz / pe

0 stars 0 forks source link

No mention of duplicate errors for new Task in UG #9

Open albertsutz opened 2 years ago

albertsutz commented 2 years ago

image.png

nus-pe-script commented 2 years ago

Team's Response

From google, definition of "already":

before or by now or the time in question.

Definition of "exist":

occur or be found, especially in a particular place or situation.

Therefore, "already exist" should be interpreted as:

can be found by the time in question

Which means that the task can be found by the time the command is run. This means that inside of the application, it can be found already. Why can such a task be found? Because it is already inside the application. So when a user is trying to put in something that is already inside the app, then the user is trying to put in an identical "something", ie a duplicate.

Rejected.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I understand your point. But the response does not answer my issue. I understand that this is a duplicate task as that is exactly my intention. The issue is that it is not described in the UG (as stated in my Issue Title).

This is also the reason why I put DocumentationBug and not FeatureFlaw or FunctionalityBug.

The issue is that

  1. The users might not even know that duplicate is not permitted

  2. Even if, Say that the users know number 1 (which can be seen from the error message)

    1. the users will not know what is considered as duplicate Task in this case as there is no indication (both in the UG and the error message) image.png

    2. If you see the screenshot above, you'll see that even the same thing (with just one typo of capital letter but with same description and same time) will not count as duplicate, which can be confusing for users. Therefore, I feel that this is not as trivial as the team's response seems to indicate.

I believe that the issue is valid and reasonable.