Bug 1471781 - SUI : When orders are duplicated , only one order is shown in shopping cart
SUI : When orders are duplicated , only one order is shown in shopping cart
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API (Show other bugs)
Unspecified Unspecified
medium Severity medium
: GA
: cfme-future
Assigned To: Gregg Tanzillo
Nandini Chandra
Depends On:
  Show dependency treegraph
Reported: 2017-07-17 08:32 EDT by Nandini Chandra
Modified: 2018-07-13 01:54 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screen shot of shopping cart with single order (51.40 KB, image/png)
2017-07-17 08:35 EDT, Nandini Chandra
no flags Details

  None (edit)
Description Nandini Chandra 2017-07-17 08:32:28 EDT
Description of problem:
When orders are duplicated in SUI, only one order is shown in the shopping cart.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Provision a few services in SUI.
2. Click on any order with a VM and duplicate.
3. Duplicate the same order from step 2 or duplicate a different order.

Actual results:
Only one order is shown in shopping cart.

Expected results:
All the duplicated orders should be shown in shopping cart.

Additional info:
Comment 2 Nandini Chandra 2017-07-17 08:35 EDT
Created attachment 1299842 [details]
Screen shot of shopping cart with single order
Comment 3 Allen W 2017-07-17 10:04:43 EDT
When an order is duplicated it replaces the contents of the cart each time, the duplication of multiple orders will never "add up" per sey.
Comment 4 Allen W 2017-07-17 10:21:21 EDT
Looking to close this as the duplication behavior is in line with api behavior, duplicating an order clears the cart each time rather than adding it all together.
Comment 5 Chris Kacerguis 2017-07-17 10:47:48 EDT
Ok.  Sending this to the API team for comments.  Not really sure if we want to leave it as-is or change it.  I'll leave that to the API team to decide.
Comment 6 Chris Kacerguis 2017-07-17 10:49:18 EDT
Gregg - So, the API is worked as expected, however to QE's point...it's an odd experience.  I'm not sure *if* we should change it, and what the implications would be for the user base as a whole.

Sending the ticket for you to make that call (either way is fine for us, just let us know).

Note You need to log in before you can comment on or make changes to this bug.