nus-pe-script
commented
6 months ago Team's Response
While we agree that this can lead to inconvenient scheduling errors, this is still intended behaviour as it is our workaround for allowing group interviews (which is a planned enhancement as stated in the DG). More specifically, instead of Hiring Managers adding 1 interview with multiple interviewers and applicants, they can add multiple interviews at the same date and time for the same interviewers/applicants to signify a group/panel interview. In the next iteration when we implement group/panel interviews, we will disallow users from adding interviews at the same date/time for the same interviewers/applicants.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: I think that this bug should be addressed in the current iteration of the app. While it is mentioned in the documentation that you are planning to add group interview in the future, but when the hiring manager who is your user read the UG, they will assume that group interview would not be working so they will not expect the app to handle group interviews. This meant that they will just be using it for single interviews. And in this use case, the bug of allowing the same interviewer to go into different interview at the same time slot, without any sort of warning could lead to some huge inconvenience in the hiring process, causing problem for not only the manager, but also the applicant and the interviewer. Since the app is all about assisting in the hiring, this bug should definitely be resolved in current iteration.
## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** I would argue that this is more of a functionality bug than a documentation bug, because this is more about a functionality of an app not working as expected and not about a crucial missing step or error in the documentation that cause the scheduling issue for the user. Just because you did not mention a functionality error in the documentation, it does not make it more of a documentation bug than a functionality bug, as by this logic, all functionality bugs could be argued as documentation bugs.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** As stated earlier, the potential worst case of this bug can affect a wide group of people and cause noticeable problem in the hiring process for the hiring manager.
Currently, the app allows the same interviewer to be in two interviews at the same time slot as seen in the provided screenshot. The interviews being separate items in the interview list implies that they are different interviews. In the worst case, the hiring manager could mistakenly assign an interviewer, since the app allows this, into the two different interviewers on the same time slot and this could cause some issues with the hiring process.