nus-pe-bot
commented
4 years ago Team's Response
Firstly, it is stated in the UG that the columns can be resized as shown in the screenshot below:
However, it was not promised as a feature that all the resized column will remain in its original resized width when a new transaction is added or deleted, throughout the application usage. It only states that if the words are truncated, you may resize the columns which the tester may have incorrectly inferred to have meant that columns would remain resized throughout the application usage but it was not meant to do that and has to be done everytime you would like to view the truncated transaction.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: The reason I posted this as an issue is exactly because the feature did not function in the way that was expected, therefore was treated as a bug. If the UG had mentioned that the columns would reset if a new operation took place, then this would not be a bug but rather a feature flaw as this is still extremely unintuitive. Rejecting the issue as "it was not mentioned in the UG" is not acceptable, and I honestly suspect an attempt on the team's part to game the system by heavy-handedly rejecting issues.
As to why this issue is problematic, I would like to consider some other applications with resizeable/re-orderable columns.
-
Excel: Excel has the ability to resize columns. If I were to provide an analogy for the behavior in the application, it would be like if Excel reset their columns to the original size every single time the user were to input a command into the command bar.
-
Sourcetree: I believe that you use Sourcetree to manage your commits. Sometimes, the graph gets too wide to be displayed, so you would resize the column to show the full graph. Sourcetree keeps the same column widths when switching branches, much like how the application should keep the same column widths/order when adding/sorting/deleting entries.
-
IntelliJ: Same as the above.
When you give the user an option to resize/reorder, it means that the user expects to be able to customize their display. Imagine a frustrated user spending time reordering and resizing the columns, and when they perform a single operation all their previous work is undone. This isn't just a minor frustration either. Note that this issue isn't restricted to the home tab but also the reimbursements, inventory and cashier tabs as well, so it is very possible that they have spent a significant amount of time on customization. What the response said was that the user should have somehow expected that the columns would be reset, which I believe is absolutely ridiculous.
The columns in the home tab can be resized or reordered by dragging the border. However, after I add or delete a transaction, the columns reset to the default size. To replicate, manually resize the columns and add/delete a transaction.
Before adding:
After adding using command
add dt/24-Aug-2019 d/Printer ink c/Miscellaneous a/3.50 p/Alex Yeoh: