search

yimjianbing / pe

0 stars 0 forks source link

Unable to look at my list of orders while executing other commands #7

Open yimjianbing opened 4 days ago

yimjianbing commented 4 days ago

By having the user be forced to repeatedly use the command "listOrder" just to see the list of orders make it very hard for a user to repeating add orders to a customer, if he were to have multiple different orders he wish to add to a specific customer, he would have to repeatedly input put [ORDER] [n/NAME], followed by listOrder again if he wants to see whats the next order to put, and it makes it really inconvenient to use the order feature overall, reducing the usability of NomNomNotifier severely.

image.png

I think the dev team can consider adding a GUI to show the list of orders somewhere so that there is no need to repeatedly call listOrder, only for the next command to cause the list of orders to disappear

nus-pe-script commented 18 hours ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

This issue raises the same concern as per the one in #2901. Our response is the same:

Thank you for the suggestion! While we understand the idea of a dedicated GUI list for orders, this feature is not critical for restaurants—our primary user group. Restaurants typically have well-established workflows and are already familiar with the orders they handle, making a GUI-based visualization less important for their operations.

Our current focus is on developing features like order tracking, which we believe are more impactful for restaurants’ day-to-day activities. This feature is also not within the current scope of the application, which was designed with a command-line approach to order management. The feedback provided after adding an order (New order added: cake) confirms the action, and users can retrieve the full list of orders using the listOrder command. This design keeps the interface simple while ensuring all necessary functionality is accessible without overcomplicating the GUI.

Additionally, this application is intended to complement existing workflows where employees can efficiently manage orders without heavily relying on the app for visual order management. As such, GUI enhancements like this currently have a lower priority on our roadmap.

While we acknowledge the potential for future GUI enhancements, implementing a dedicated GUI list for orders would significantly change the app’s design and is not a focus at this time. Thank you for your understanding and for helping us refine our app!

The 'Original' Bug

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

Separate list for orders in the GUI

Perhaps, there could be a separate list within the GUI for orders added. This will make it easier to view and make changes to it when necessary. This leads to extra steps such as listing orders through the listOrder command.

Moreover, as a user, I was expecting to see an order within my list after the command order cake. Currently, I only get the feedback that: New order added: cake

[original: nus-cs2103-AY2425S1/pe-interim#3961] [original labels: type.FeatureFlaw severity.Low]

Their Response to the 'Original' Bug

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

Thank you for the suggestion! While we understand the idea of a dedicated GUI list for orders, this feature is not critical for restaurants—our primary user group. Restaurants typically have well-established workflows and are already familiar with the orders they handle, making a GUI-based visualization less important for their operations.

Our current focus is on developing features like order tracking, which we believe are more impactful for restaurants’ day-to-day activities. This feature is also not within the current scope of the application, which was designed with a command-line approach to order management. The feedback provided after adding an order (New order added: cake) confirms the action, and users can retrieve the full list of orders using the listOrder command. This design keeps the interface simple while ensuring all necessary functionality is accessible without overcomplicating the GUI.

Additionally, this application is intended to complement existing workflows where employees can efficiently manage orders without heavily relying on the app for visual order management. As such, GUI enhancements like this currently have a lower priority on our roadmap.

While we acknowledge the potential for future GUI enhancements, implementing a dedicated GUI list for orders would significantly change the app’s design and is not a focus at this time. Thank you for your understanding and for helping us refine our app!

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

## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]