Open ShenyiCui opened 1 year ago
We believe that your example is not representative of a one-day stay as in a hotel, the check-in time of a guest is typically after their check-out time. Hence, for a one-day stay, the date range should be 27-02-22 to 28-02-22. For example, this is taken from one of the hotels that are included in our target users.
Team chose [response.Rejected
]
Reason for disagreement: >>> the check-in time of a guest is typically after their check-out time
- The dev team's response would be valid IF they allowed time as part of their date input.
- However, the team only inputs dates and doesn't allow time input.
- It is possible for guests to want to check in at
02-22-2022 1000
and check out at02-22-2022 2200
.- Because the input of
02-22-2022
and check out at02-22-2022
isn't allowed, and since this is a valid use case, it is therefore a bug.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: Recall the definition of a medium severity:
A flaw that causes occasional inconvenience to some users but they can continue to use the product.
- It does cause occasional inconvenience to users who want to stay in a hotel for less than a day. (quite a common occurrence for motels)
Recall the definition of a low severity:
A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.
- It's definitely not unlikely, and the inconvenience caused is more than minor as it means data cannot be recorded for some guests accurately.
Expected Behaviour
Current Behaviour
How to reproduce
add n/r p/123 e/1@test.com rm/0-00 dr/28/02/22 - 28/02/22 ng/2 rq/test
Screenshots