nus-se-script
commented
10 months ago Team's Response
Documentation should clearly specified the behavior for the edit.
Items for the Tester to Verify
:question: Issue type
Team chose [type.DocumentationBug]
Originally [type.FeatureFlaw]
- [x] I disagree
Reason for disagreement: Despite this not being included in the documentation, it is also equally a feature flaw as from the UG of the team, WedLog is suppose to
simplify the complexities of wedding planning and offer an intuitive and stress-free experience guaranteed to streamline the planning process
And in this case it is considered a feature flaw as it fulfils this criteria of a feature flaw bug:
Features that don't fit well with the product
The erasure of previous tags when editing a tag is very cumbersome as users have to remember the previous tags and since weddings usually have a large number of guests (the average number of guests is 100), i believe most users would use the tags to categorise and find guests using the filter command. As such, the tags should have more flexibility in its implementation.
Furthermore, the implementation to remember previous tags and delete tags would be relatively easy to implement and should have been of a higher priority for the purpose of the app.
Initially I have a guest 8 named "Justin Soh" who already has all these tags, and i want to add an extra tag for him using edit however instead of updating the tags, it cleared the previous tags and only updated the one from the input. However, this was not specified in the UG and may be confusing for planners who want to update tags. Additionally, even if planners are aware of this, when they want to update tags in the future to better filter their guests by, it may be very troublesome to all in all the tags again