soc-se-bot
commented
9 months ago Team's Response
Such validation is impossible to implement as it is hard to determine what is a mistake and what is not if the user has a different application that is due the next day. There are too many possible variations of plausible careless mistakes, and it will be hard to account for all the possible cases. Hence we believe this is NotInScope.
Furthermore, it only brings about minor inconvenience to the user as the user can delete or edit the wrong company that they have added thus we will lower the severity from a Medium to a Low.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
With the current iteration of the application, I am able to create 2 entries for a single application that are identical in role and company, but perhaps differ due to a small difference in date.
The current definition of duplicates allows careless users to potentially enter the same application twice due to minor errors in entering deadline, which may, over time, clutter the company list in the application with "near-duplicates".