nus-se-bot
commented
11 months ago Team's Response
We intend for the name constraints to be as such as names are used as unique identifiers in FumbleLog. See assigning persons to events and assigning groups to events. Imagine exact duplicate names assigned to an event, how confusing it that!
With names as a unique identifier, it allows for FumbleLog to be less cluttered when displaying persons and groups, allowing for a cleaner GUI. This is a productivity app so reducing clutter takes precedence. People with the same name can be added with more information to make them differentiable.
This is rejected as a result.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Description
With the high volume of people expected to be added to the application, shouldn't be unique by name. Instead, the team should brainstorm other ways to ensure that duplicate contacts are not created by giving the user a warning each time the user keys in a duplicate name.
Steps to produce