search

pzl111 / pe

0 stars 0 forks source link

Having the exact same transaction but different amount does not really make sense #22

Open pzl111 opened 10 months ago

pzl111 commented 10 months ago

image.png

I believe the app should give a warning when all details are the same but the amount is opposite. It does not make sense for the exact same transaction at the exact same time to have 2 different amounts. Although this is a rare occasion hence low severity.

soc-se-bot commented 9 months ago

Team's Response

Thank you for your feedback. We have opted to classify this as a Low FeatureFlaw that is Rejected for the following reason:

This is an intentional design as described in the DG for the Transaction model: https://ay2324s1-cs2103-t16-3.github.io/tp/DeveloperGuide.html#transaction-model

Users may have recurring transactions that bear the same name and as a result, disallowing duplicate transactions can make the application too inflexible and hard for the user to adopt if they have recurring transactions that they want to log. For instance, a user might simply name all his "Buying groceries" transactions the same but each time, the amount spent can differ from one another (i.e. buying more/less on different trips)

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I think that the group should at least give a warning to the user that a possible duplicate would be entered, to let them know in case it was unintentional. This gives poor UX for the design decision chosen.