Bug: program denies adding a new entry even though they are not equal

[ShenyiCui]

Expected Behaviour

• One guest is supposed to be allowed to book two separate rooms within the same date period
• Possible use case: I want to book a room for my wife and a separate one for my children
• OR I have the same name as someone else (Very Common) I have a different email, phone number etc. but just because my name is the same as someone else I cannot book a room in your hotel.

Current Behaviour

• If a guest already exists within the system the program doesn't allow it to book two separate rooms

How to reproduce

• add n/s p/123 e/1@test.com rm/0-0 dr/28/02/22 -01/03/22 ng/3 rq/test
• add n/s p/1234 e/12@test.com rm/0-01 dr/28/02/22 - 01/03/22 ng/2 rq/test
• Error even though the email, room and phone number requested is different

Screenshots

[nus-se-script]

Team's Response

We believe that for the use case that you have provided, we allow for the same email address and phone number to be under 2 separate guests as it allows you to put your name for one room and your child's name for the other while using a single point of contact, hence solving the problem.

(The third point that you mentioned is a duplicate issue)

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: - I believe it is a bug because it is a valid use case for one person to want to book multiple rooms under his name for his family and or friends

• This is not allowed, and the workaround mentioned does not excuse this from being a bug.
• This is a bug because the dev team did not consider a common use case
• If they did consider it would be stated in the User Guide or FAQ

---

:question: Issue severity

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

• [x] I disagree

Reason for disagreement: Recall the definition of a high-severity issue:

A flaw that affects most users and causes major problems for users. i.e., only problems that make the product almost unusable for most users should have this label.

• Since this is a common use case and it causes major inconvenience for users when booking multiple rooms under one name isn't allowed it should be considered high severity.

Recall the definition of a low-severity issue:

A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.

• This flaw in the design is not a minor inconvenience to the hotel staff or guests.
• This flaw in the design will be exploited regularly as it's a common use case.

---