Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Same expense name

Steps to recreate:

1. Add a task with d/Name
2. Add a task with d/2pac
3. Edit task with Name to 2pac

UG states:

---

_{[original: nus-cs2103-AY2122S2/pe-interim#2262] [original labels: type.FeatureFlaw severity.High]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

This is our team's intended behaviour of adding expenses. We expected that users may have the same description expense with unique expense Category/date/amount and this was thus a documentation mistake on our part. This is marked as low as the behaviour is as intended and the application was built with the assumption in mind. If the user is adding the same description of an event on a different day we expect it to be valid. It is unlikely that there will be a case where either the user or the programme will not want to add in an expense with the same description but with a different expense Category/date/amount and problems will arise.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

❓ Issue type

Team chose [type.DocumentationBug]
Originally [type.FunctionalityBug]

• I disagree

Reason for disagreement: [replace this with your explanation]

❓ Issue severity

Team chose [severity.Medium]
Originally [severity.High]

• I disagree

Reason for disagreement: [replace this with your explanation]

from pe.