Open tyx021 opened 1 year ago
This has been moved to feature flaw since:
Since this problems can only happen in case of deliberate sabotage, or if such input is entered due to a user's mistake; in which case it is a lack of proper handling.
Furthermore, it is up to the user (the receptionist) to follow their organization's protocol for the maximum limit to how far in advance one can schedule an appointment, which is why it is not in scope
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
To reproduce:
appointment add --p 1 --s 2500-05-01 0700 --e 2500-05-01 0800 --v Dose 2 (Moderna)
Expected: Should reject input for appointment in year 2500
Actual: Input accepted
SS: