nus-se-script
commented
2 years ago Team's Response
We are rejecting the bug as we believe that it is useful for users to be able to add past meetings and use our archive feature to keep track of past meetings. It is useful in the case where a user might have forgotten to add the meeting until it had already happened but still wants to store the record of the meeting in the archived meeting list.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
It is possible to add/edit a meeting with a date that has already passed.
It makes sense that a meeting could have been added in the past and that the meeting has already passed but still exists in the app. However, it does not make sense that a new meeting can be added or a meeting that is upcoming can be edited to a date that has already passed unless it is for the purpose of maintaining a record (for example keeping track of all meetings using archivelist). In addition, the fact that the purpose of the meeting is to serve as a reminder for the user about upcoming meetings (using reminder), suggests that meetings that are upcoming are the ones that the user is concerned about and should therefore only allow users to add/edit meetings that has not passed or passed meetings should not appear in the meeting list as it confuses the user into thinking that the meeting has yet to come.
This seems to be a feature problem and the severity should not be very low as it is not just a cosmetic issue and is more likely a issue that might confuse users.