You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have at least 1 customer, 1 product and no orders initially. (0 orders)
Enter multiple valid order commands.
Enter valid command to add product to order.
Expected: Expected the orders created to be reflected in GUI
Actual: GUI shows a message to add a product to the orders
Rationale (includes explanation of severity):
If the app starts from a clean slate (step 1 of how to reproduce this problem), there are no orders initially. Then, when the user adds multiple orders without products in succession, they are only prompted on how to add a product to the orders. This is slightly misleading as it does not tell the user if the order has been created, and personally, I would assume that the order is created but not shown.
Then, the multiple orders created are not reflected on the GUI, which does not allow users to see how many existing orders there are.
If the user wants to add a product to any of the multiple orders, they cannot do so as the product will only be added to the latest order, and for previous orders created, while they actually do not exist, this is not shown to the user. While this way of order creation may not be the intended usage (hence Medium), it can be avoided and improved on.
Recommendation/Suggestion:
Reflect the orders in the GUI after an order
has been successfully created. Or, provide a command to show the number of existing orders and another command to show order details given the order index.
Or, state in documentation the combination of having to use order and product commands in succession to create an order, and if done otherwise, the order is not actually created.
The text was updated successfully, but these errors were encountered:
[This is the team's response to the above 'original' bug]
This is an intended feature as we believe that we should only show an order when it had products in it, as creating an order without products might be a mistake so we delay showing the order until the user has added a product to it, since orders are meant to exist in tandem with the products they contain. So rest assured the order is there, after adding a product, the user will promptly be able to view the order.
Items for the Tester to Verify
❓ Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
I disagree
Reason for disagreement: [replace this with your explanation]
❓ Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
I disagree
Reason for disagreement: [replace this with your explanation]
Steps to reproduce:
order
commands.Expected: Expected the orders created to be reflected in GUI
Actual: GUI shows a message to add a product to the orders
Rationale (includes explanation of severity):
If the app starts from a clean slate (step 1 of how to reproduce this problem), there are no orders initially. Then, when the user adds multiple orders without products in succession, they are only prompted on how to add a product to the orders. This is slightly misleading as it does not tell the user if the order has been created, and personally, I would assume that the order is created but not shown.
Then, the multiple orders created are not reflected on the GUI, which does not allow users to see how many existing orders there are.
If the user wants to add a product to any of the multiple orders, they cannot do so as the product will only be added to the latest order, and for previous orders created, while they actually do not exist, this is not shown to the user. While this way of order creation may not be the intended usage (hence
Medium
), it can be avoided and improved on.Recommendation/Suggestion:
Reflect the orders in the GUI after an
order
has been successfully created. Or, provide a command to show the number of existing orders and another command to show order details given the
order
index.Or, state in documentation the combination of having to use
order
andproduct
commands in succession to create an order, and if done otherwise, the order is not actually created.The text was updated successfully, but these errors were encountered: