[docs-schedule expiry]

[yusufaine]

While it makes sense for schedules to expire after its session, I see a use case where that might be bad, for instance, if the user themselves forgot about the interview that day, opens the app the next day, and it's marked as completed.

Perhaps it would be better to leave them as is or use a new status to denote that the interview was missed.

[nus-se-script]

Team's Response

The intended purpose of the application is to help the user keep track of the interviews and avoid scheduling interviews with clashing time slots. Therefore keeping the interview schedule less clustered by automatically removing expired interviews and marking candidates as completed is intended within the scope of v1.4. Hence our team chose to label this report as not in scope based on the suggestion from the tester - such additional tags on new status are considerations for the future, but are not considerations that might cause the current app to misbehave or crash.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---