search

ltzehan / pe

0 stars 0 forks source link

Misleading file creation message #2

Open ltzehan opened 1 year ago

ltzehan commented 1 year ago

On a fresh start of the application, the user is notified of "SniffAppointments.txt" being created. However, there is no such file being created in the directory where the JAR file is being run but is definitely getting saved since the next startup loads previously saved data correctly.

This will be confusing to most users as the path to the actual file is not stated, and will make transferring data between devices difficult as the save file cannot be located.

Steps to Reproduce

consultation at/Cat an/Lulu on/Jon cn/91919191 cd/2023-12-12 ct/19:00
bye

image.png

soc-se-bot commented 1 year ago

Team's Response

Bug is a duplicate as it is due to the failure to mention the location of the save file.

The 'Original' Bug

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

Save File

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

Untitled16.png

There is an FAQ on how to transfer save file data but no instructions on how or where to locate the save file. As a user, I am unable to locate the save file myself easily and this hinders my ability to transfer my save file data.

[original: nus-cs2113-AY2223S2/pe-interim#2840] [original labels: severity.Low type.DocumentationBug]

Their Response to the 'Original' Bug

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

Bug is accepted as we failed to mention the location of the save file.

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

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** If this is considered as a documentation bug, this should at least be a medium-severity bug as this is an important omission that will affect more than a small handful of users. Not being able to access the save file effectively disables the portability feature of the application.