nus-pe-bot
commented
3 years ago Team's Response
As mentioned in the UG, FAQ:
Q: Why are the identifiers of my Events not in counting order? A: Identifiers are meant to be unique to each task. Whenever a new Event is created, the identifier counter increases. The counter does not decrease since this could potentially lead to issues whereby the identifier is no longer unique, which would cause the functionality of Focuris to be compromised. As such, we believe that an identifier that does not reset or decrease in a single session is best suited for such a task.
This is not a bug, as we emulate the functionalities of the likes of GitHub and Jira, who use unique incrementing identifiers, rather than using indices for tasks. This is so there's a way to reference back to tasks in the future if we grow Focuris into a bigger application.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Because the identifiers are unique and stick with the respective event, when events of smaller identifiers get deleted, the rest stay the same.
However, this means that after the users keep using the app for a long time, all their identifiers will have very large numbers, which can cause clutter or be confusing/overwhelming to look at.