Skip to content

Shopping cart items submitted for approval before ordering #23242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rafi-br opened this issue Oct 18, 2024 Discussed in #23238 · 2 comments
Open

Shopping cart items submitted for approval before ordering #23242

rafi-br opened this issue Oct 18, 2024 Discussed in #23238 · 2 comments
Assignees

Comments

@rafi-br
Copy link

rafi-br commented Oct 18, 2024

Discussed in https://github.com/orgs/ManageIQ/discussions/23238

Originally posted by rafi-br October 17, 2024

Hi there,

my understanding is that we can first add the multiple items to the MIQ shopping cart and on pressing the order button , they will be submitted for the approval. However , what I have noticed is that the added items to the shopping cart are immediately submitted for the approval before even the order button is pressed. Not sure if I am missing some configuration or its a bug. can some one help me with this.

I have noticed this with manageiq/manageiq:oparin-1.1 and the recent version manageiq/manageiq:quinteros-2.1
shoppingCart
senttoapproval

@GilbertCherrie
Copy link
Member

GilbertCherrie commented Jan 20, 2025

@Fryguy I think this is an API issue. The UI is calling this API endpoint to add it to the cart.

return CollectionsApi.post('service_orders/cart/service_requests', null, null, { action: 'add', resources: [ request ] })

But after this API call is run to add it to the cart it is also ordering it which is why it shows up in the UI-Classic reports table. It seems like the API is both adding it to the cart and ordering it at the same time with this API call.

@miq-bot miq-bot added the stale label Apr 21, 2025
@miq-bot
Copy link
Member

miq-bot commented Apr 21, 2025

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants