nus-se-bot
commented
12 months ago Team's Response
While it would be nice for the user to record the ending time for a meeting, we valued the speed where we can add meetings more than recording the end time of the meeting. This is because usually when attending the meeting you would just want to know when it starts so you can attend it on time but the end time is usually not as important. In fact, it is very common for meetings to end earlier or even later than expected and usually if that was the case, users using NoteNote would likely not edit the end time to the actual ending time and might even cause confusion when they refer back to the meeting details some time in the future.
Based on the above, we decided that this feature was not as important as our focus which is to take notes and hence classified this issue as NotInScope instead of rejecting it.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: Thank you for explaining your decision on the meeting ending time feature. While I understand the focus on speed, the ability to specify the end time is a fundamental aspect of meeting management. Furthermore, if speed really were a priority, specifying the ending time for a meeting could be made optional.
Although you mention that the focus is on making notes, the UG does that state
With NoteNote, you can swiftly record notes, organize contacts, and schedule meetings—all through quick keyboard commands.
Users often need to plan their schedules accurately and having both start and end times is essential for meeting management. It's a basic functionality that aligns with the core purpose of a meeting management app, and the lack of functionality here would inconvenience most users of the application. As such, I consider this issue to be within the scope for this application.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
Currently, the application does not allow the user to specify/record the ending time for a meeting. Most users managing their meetings would want to remember the start and end times of the meetings to be able to schedule them properly without overlap.
Thus, there should be the ability to specify ending time for a meeting.