nus-pe-bot
commented
3 years ago Team's Response
Same as Meeting time should not be in the past.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Meeting time should not be in the past
Expired meetings with reference to present time should not be added, not does add value to the proposed functionality of scheduling future meetings
Although can be considered for archiving for future implementation
[original: nus-cs2103-AY2021S2/pe-interim#1220] [original labels: severity.High type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
We did not restrict the addition of meetings because it would be adding a layer of unnecessary complexity and reduced flexibility for user. Also a user can keep track meetings or schedules that happened in the past as a record, so he might need to edit or add meetings into the past.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue severity
Team chose [severity.High]
Originally [severity.Low]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
It would be better to only allow adding meetings that are occuring in the future. Currently, past meetings are allowed to be added, which might not suit the purpose of the product.
example: an event happened in 2020 is allowed to be added