Skip to content
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

Rest API Magento 2.4 order update overwrites existing item information #28483

Merged
merged 5 commits into from
Jun 25, 2020

Conversation

engcom-Charlie
Copy link
Contributor

Description (*)

Fixed and covered by tests.

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Rest API Magento 2.4 order update overwrites existing item information #22431

Manual testing scenarios (*)

See #22431

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jun 3, 2020

Hi @engcom-Charlie. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

@engcom-Charlie
Copy link
Contributor Author

@magento run all tests

@ghost ghost added the Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. label Jun 3, 2020
@ghost ghost assigned ihor-sviziev Jun 3, 2020
@ihor-sviziev ihor-sviziev added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jun 3, 2020
@ghost ghost assigned engcom-Charlie Jun 3, 2020
@engcom-Charlie
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor

Looks like failed integration test not related to changes from this PR. Approved ✅

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-7612 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

engcom-Alfa commented Jun 4, 2020

✔️ QA Passed

Manual testing scenario:

  1. Place an order with a product with a customizable option.
  2. On the order item in the database the custom options are stored in the sales_order_item table, product_options field in the info_buyRequest as "key": "value" pair.
    Screenshot from 2020-06-04 13-24-23
  3. Update the order using the Rest API (f.e. just hold order).
    Send POST request /V1/orders/{id}/hold
  4. In the sales_order_item table check custom_options column;

Before: ✖️ The info_buyRequest data are changed

Screenshot from 2020-06-04 13-26-06

After: ✔️ The info_buyRequest remain as they were before the API Update

Screenshot from 2020-06-04 12-46-52

It was checked with Unhold, Comments, Email, Cancel, also Simple, Bundle, and Configurable products.

@engcom-Echo engcom-Echo self-assigned this Jun 4, 2020
@engcom-Echo
Copy link
Contributor

@magento run Integration Tests

@engcom-Echo engcom-Echo added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jun 5, 2020
@slavvka slavvka added this to the 2.4.1 milestone Jun 9, 2020
@slavvka slavvka added the Priority: P3 May be fixed according to the position in the backlog. label Jun 9, 2020
@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Jun 17, 2020
@slavvka
Copy link
Member

slavvka commented Jun 24, 2020

@magento run all tests

@slavvka
Copy link
Member

slavvka commented Jun 24, 2020

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Jun 25, 2020

Hi @engcom-Charlie, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage Component: Sales Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Rest API Magento 2.4 order update overwrites existing item information
6 participants