No end time for Events

[HanB1n]

When keeping track of Events in the real world, it is highly likely there is a start and end timing/ date. Most other event tracking application out there would support this. I would think most users would be turned away by an event tracking application that cannot store the end timing.

You can consider an additional optional field for the Event to store end timings.

[nus-pe-bot]

Team's Response

Thanks for submitting this report.

Comments from dev team: Rejected

Bug Type that we chose: Feature flaw

Severity that we chose: [severity] Low

Decision that we made: Our team decided not in scope as this feature was deprioritized given the time constraints. Would have added it in future iterations

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** Severity.Low should be for flaws that are rare to normal users. However, as explained, majority of users would plan events or have events that have both a start and end time in the real world. This causes occasional/ frequent inconvenience to the users which should have the Severity.Medium tag. Also, this is a relatively easy feature to implement given dates have already been implemented.

---