search

audipras / pe

0 stars 0 forks source link

Downloading a `.csv` file overwrites the previous `.csv` file. #6

Open audipras opened 1 week ago

audipras commented 1 week ago

Downloading a new .csv file overwrites the previous downloaded .csv file, probably because they both get named exported.csv.

Steps to reproduce:

  1. Download a .csv file by using the download command.

  2. Download a different .csv file (e.g. by running download t/Bye).

Expected: Both .csv files are present, with the latest file added being named exported(1).csv.

Actual: Only the latest file is present.

Screenshots: After running step 1:

image.png

image.png

After running step 2:

image.png

image.png

soc-se-bot commented 1 week ago

Team's Response

Thank you for reporting this issue. We understand your concern about the .csv file being overwritten when exporting multiple files. However, this behavior is intentional and designed to meet the practical needs of our primary users, restaurants.

Restaurants typically require the most up-to-date data in a single, easily accessible file rather than managing multiple exported files. Allowing multiple files with varying names could lead to clutter and confusion, especially in fast-paced environments where employees rely on quick access to accurate data. Overwriting the previous file ensures users are always working with the latest information without needing to manually sort through or delete outdated files.

Moreover, exporting multiple files serves little practical purpose for restaurants. Restaurant operations usually revolve around a single set of up-to-date order or customer data at any given time. Multiple .csv files with similar data would add unnecessary complexity, as staff would need to identify which file is the most recent before proceeding, increasing the chances of error.

This approach also aligns with the app’s focus on simplicity and operational efficiency. For users who wish to keep older exports, it is possible to manually rename the file before initiating a new export.

Given these reasons, we do not consider this behavior a bug but a deliberate design choice to prioritize usability and efficiency for our target audience.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Since this is a deliberate design choice, the bug type should be changed to a documentation bug, since there is no mention of this in the user guide. Although the design philosophy is fair, the user could lose hours worth of work and data analysis if they were to edit the data file in the original data folder without renaming it, by running the download command again (to, for example, get the latest data). The file with their work would get overwritten and lost forever. Since countermeasures against this bug requires the user to be aware of this design choice, this should be present in the user guide.

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** Since the user can lose hours worth of work and data analysis from their data file being overwritten due to there being no mention of this behavior in the user guide, this bug definitely classifies as a severity medium.