search

Jianwen0451 / pe

0 stars 0 forks source link

Payment status is not saved #3

Open Jianwen0451 opened 3 days ago

Jianwen0451 commented 3 days ago

Screenshot 2024-11-15 at 4.52.13 PM.png

The payment status of the appointment is not saved after restarting the program

To reproduce this

  1. Add an appointment with a person
  2. Set the status of payment to Paid
  3. Exit the app
  4. Reopen the app
  5. View the payment status

This is a severe bug as it will strongly hinder the user that an appointment can not be marked as paid.

nus-pe-bot commented 10 hours ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

No details provided by team.

The 'Original' Bug

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

Payment status not saved

Issue

Paid status does not seem to be saved upon reopening application.

How to replicate

  1. open jar file in fresh directory
  2. add n/John Doe p/98765432 e/johnd@example.com a/311, Clementi Ave 2, #02-25 t/back pain t/ankle sprain
  3. schedule john doe d/2024-11-29 0900 note/p
  4. payment john doe d/2024-11-29 0900 pay/paid
  5. view john doe observe that pay status is Paid
  6. exit application using command
  7. reopen jar file
  8. view john doe again. observe that pay status is Unpaid despite step 4

image.png

[original: nus-cs2103-AY2425S1/pe-interim#599] [original labels: severity.Medium type.FunctionalityBug]

Their Response to the 'Original' Bug

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

Thank you for raising this issue.

However, we would think that this is of a severity low issue as this issue only occurs when we restart the application. The app is designed with the assumption that it will run continuously in typical usage scenarios, meaning that restarting the application would be a rare occurrence. Users can still view and update payment status during a single session without any issues. The only inconvenience arises when the app is restarted which can be easily remedied by manually updating the status such as through checking against the official payment receipts. Hence, this issue does not prevent users from performing key operations.

Items for the Tester to Verify

:question: Issue duplicate status

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

Reason for disagreement: [replace this with your reason]

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]