Incorrect message generated from extra tag when adding a flight

[chydarren]

The issue is that when I have two flight number tags in my input, it will generate the wrong error message (i.e. designated gate is already occupied). The system should first capture which is the correct flight number tag before producing other kinds of error messages.

[nus-pe-script]

Team's Response

Invalid bug because bug was still caught, just in a different priority from the tester.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: It is possible for a user to enter duplicate tags accidentally, and in this application, this accident is not being caught despite the team's argument. To ensure that what they have said is valid, i.e. "bug was still caught", I re-try it with two non-existent flights in the list, and somehow the error by the user is not caught. Kindly see the image below as a reference, thank you.

In fact, there is no error message generated when the user enter duplicate tags, this indicates that no attempt was made to catch duplicate tags being entered for fn/<flight_no>. Moreover, the below example adds the flight number 403 and ignores the user's initially entered 402 at the front, and user is not informed.

---