Able to add a past date for Contract-End-Date field

[linette-g]

Currently able to add a contract end date with a past date (e.g. 2020-01-01) which is counter-intuitive given the context of managing potential hires and employees. Not restricting this seems to bring more harm than good since the target user would likely not want to input an incorrect contract end date that is in the past (since the contract should not have ended yet).

I understand that this would give additional flexibility to users (as mentioned above), but the given flexibility could possibly result in more errors of inaccuracy for the target users. Not sure when the target user would want to document past employees or when this flexibility would be useful given the context (perhaps could mention/elaborate in the user stories?).

[soc-se-bot]

Team's Response

Reason for dropping to severity low

This issue is should be a low as the user intentionally added contract end dates in the past which is a rare situation as they intentionally inputted inaccurate data.

Reason for not in scope

Mentioned in the UG as not supported.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: The additional effort required for restricting past dates seems less than the benefit it brings since being able to enter a past contract-end-date could cause confusion about an employee's current employment status and potentially lead to payroll errors or legal compliance issues, which HR managers would not want.

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---