Open yaojiax opened 1 year ago
Indeed a flaw, should have an error message stating that is not possible, however severity should be low since it is unlikely that the user will set the same date of birth to be after date of joining. Not a priority to do in the current implementation so marked as "not in scope".
Team chose [response.NotInScope
]
Reason for disagreement:
According to the guidelines, while it is indeed true that rectifying it is less important, there are (1) no mentions in the UG that this is not supported/is a feature that is coming soon and (2) the software does not fail gracefully and just takes in the input, instead of even providing an error message.
It doesn't make sense that an employee is born before he joins, there should be input validation here as Date of Joining should be set after Date of Birth.