Skip to content

Credit Memo with Zero Total: Order Status "Complete" and not "Closed" #29023

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

Merged
merged 5 commits into from
Aug 8, 2020

Conversation

engcom-Echo
Copy link
Contributor

@engcom-Echo engcom-Echo commented Jul 7, 2020

Description (*)

Fixed Issues (if relevant)

  1. Fixes Credit Memo with Zero Total: Order Status "Complete" and not "Closed" #22762

Manual testing scenarios (*)

See: Fixes #22762

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 Jul 7, 2020

Hi @engcom-Echo. 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-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@rogyar rogyar added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jul 8, 2020
Copy link
Contributor

@rogyar rogyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The failing tests are not related to the current change. The same tests are being failed for other recent PRs

@magento-engcom-team
Copy link
Contributor

Hi @rogyar, thank you for the review.
ENGCOM-7798 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Manual testing scenario:

  1. Create order with zero Amount (all Grand Total, Total Paid, Total Refunded, Total Due, Subtotal, Shipping & Handling, Tax are zero ) in status = "Pending" and 1 SKU qty = 1;
  2. Create Invoice and now Order is status = "Processing";
  3. Ship Order -> now Order status is = "Complete";
  4. Now create Credit memo and refund and return a product;

Before: ✖️ Order Status is "Complete"

2020-07-14_14-41

After: ✔️ Order Status is "Closed"

2020-07-14_14-54

@engcom-Kilo engcom-Kilo self-assigned this Jul 14, 2020
@engcom-Kilo engcom-Kilo added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jul 14, 2020
@engcom-Alfa engcom-Alfa added the Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. label Jul 14, 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 Jul 14, 2020
@engcom-Kilo
Copy link
Contributor

@magento run all tests

@ghost ghost added the Progress: accept label Jul 15, 2020
@simonmaass
Copy link

would be great if this makes it in 2.4

@ghost ghost added Severity: S1 Affects critical data or functionality and forces users to employ a workaround. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. and removed Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Jul 16, 2020
Copy link
Member

@slavvka slavvka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@engcom-Echo Please fix the failing MFTF static checks that were recently introduced:

Test AdminCreateCreditMemoWithZeroPriceCheckOrderStatusTest is missing the required annotations: stories, severity

@slavvka
Copy link
Member

slavvka commented Jul 17, 2020

@magento run Functional Tests CE

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo engcom-Echo requested review from slavvka and rogyar July 21, 2020 10:46
@magento-engcom-team
Copy link
Contributor

Hi @rogyar, thank you for the review.
ENGCOM-7798 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

@m2-assistant
Copy link

m2-assistant bot commented Aug 8, 2020

Hi @engcom-Echo, 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 Component: Catalog Component: Sales Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Credit Memo with Zero Total: Order Status "Complete" and not "Closed"
7 participants