Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[json editing] Invalid json data is destructive #3

Open
HugeNoob opened this issue Nov 17, 2023 · 1 comment
Open

[json editing] Invalid json data is destructive #3

HugeNoob opened this issue Nov 17, 2023 · 1 comment

Comments

@HugeNoob
Copy link
Owner

HugeNoob commented Nov 17, 2023

Description

If a user edits the json data and makes two users have the same name, the data will not be loaded properly into the application.

Steps to reproduce

Change two persons to have the same name in the json.

image.png

Expected behaviour

Error message stating data is not valid. Or some warnings guide.

Actual behaviour

Application loads with no data.

image.png

Elaboration of labels

The main reason why I put high severity is because the application saves data on exit.

Consider this scenario:

  1. I want to make fast edits, hence I edit the json directly.
  2. I genuinely forgot that there is a John already in my list, and accidentally change another person's name to John.
  3. I open the application and notice all my data is gone.
  4. I quit and restart the application in panic.
  5. Step 4 wipes my invalid data completely, making me lose all my progress of wedding tracking.

Functionality bug because it is a legitimate user behaviour that may happen.

@nus-pe-script
Copy link

nus-pe-script commented Nov 20, 2023

Team's Response

Marked NotInScope as Prof has stated in the forum that "Recovering from improper edits to the data file (or other config files) was not an expectations at v1.4, unless you specifically stated such a feature in the UG." (Link)

Furthermore, we believe that even if this report was valid, it should be of Medium severity as:

  1. We believe this product only inconveniences a small subset of users as not many users would be comfortable enough with technology to want to edit the json directly.
  2. Point (1) is especially true for our target audience (wedding planners).

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

  • 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]


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants