Repository navigation
API salesRefundInvoiceV1 does no save invoice ID on credit memo #11669
Copy link
Copy link
Closed
Labels
Fixed in 2.2.xThe issue has been fixed in 2.2 release lineThe issue has been fixed in 2.2 release lineFixed in 2.3.xThe issue has been fixed in 2.3 release lineThe issue has been fixed in 2.3 release lineIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseThe issue has been reproduced on latest 2.3 release
Description
Preconditions
- Magento branch 2.2-develop
Steps to reproduce
- Place an order with an online payment method (Paypal)
- Create an online invoice for the order
- Use API method salesRefundInvoiceV1 to create a refund for the invoice
Expected result
- Because I'm refunding an invoice, I'd expect the invoice ID to be saved on the credit memo.
- When I create a credit memo from the invoice in the admin pages, the invoice ID is saved on the credit memo
Actual result
Metadata
Metadata
Assignees
Labels
Fixed in 2.2.xThe issue has been fixed in 2.2 release lineThe issue has been fixed in 2.2 release lineFixed in 2.3.xThe issue has been fixed in 2.3 release lineThe issue has been fixed in 2.3 release lineIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseThe issue has been reproduced on latest 2.3 release

Activity
magento-engcom-team commentedon Oct 24, 2017
@ajpevers, thank you for your report.
We've created internal ticket(s) MAGETWO-82601 to track progress on the issue.
okorshenko commentedon Nov 27, 2017
The issue has been fixed and delivered to 2.2-develop branch. Will be available with upcoming patch release
magento-engcom-team commentedon Jan 30, 2018
Hi @ajpevers. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1296 by @magento-engcom-team in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming patch release.
⏫ Forwardport of magento#11670 to 2.3-develop branch
Merge forwardport of magento#11670 to 2.3-develop branch
🔃 [EngCom] Public Pull Requests - 2.3-develop