nus-se-bot
commented
1 year ago Team's Response
Hello, thank you for taking the time to check the CSV file itself!
We do not agree that this is a bug. Microsoft Excel automatically casts certain texts to different display formats. It is purely cosmetic, unless it is saved over the current file (which incurs some warnings). If you open it elsewhere (e.g. in a text editor), you can see the proper info; it is indeed saved properly.
Below is a screenshot to show the difference. Both instances are open at the same time, and of the same file.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thank you for your response regarding the issue of data being automatically casted in Microsoft Excel when exported from your application. While I understand your rationale for this behavior, I respectfully disagree with your conclusion that this is not a bug.
In my opinion, it is reasonable for users to expect that the same data should be exported and displayed consistently across different programs and text editors for .csv files. Moreover, considering the fact that Microsoft Excel is one of the most widely used applications for viewing and analyzing .csv files, it is important for your product to ensure that data exported using your "export" command is consistent in format and displayed properly in Excel.
Additionally, I considered this as a bug since there are some approaches to work around and prevent Excel to automatically cast the data format. For example, use "10~19" instead of "10-19" so that it would properly display in Excel. In other hand, if your team expects users to view .csv file like the first image in your response then maybe .csv is not a good choice of design to export as since this could be less problematic using .txt.
In case your team really expect users to not use Excel opening the .csv exported files from the product, this could come down to a documentation bug because this issue is pretty notable and should be mentioned or noticed in the User Guide for how common Excel is for users with average background to use for .csv files.
After checking out the current overview by age "checkout a.csv", the 2nd tuple of a.csv file has date type value under "binName" (it supposed to be 10-19 like the picture above) column while the others have values of integer range (xx - yy where xx, yy are integer)