RMA product

[warehouseg-sp]

Preconditions and environment

• Magento ver. 2.4.8-p2
• Anything else that would help a developer reproduce the bug
  Hello,

There appears to be a problem with the return merchandise order (RMA). As shown in the screenshot, several orders are displayed, but product information is missing for most of them. Only one product is displayed, while for the others, there is no information about which product was returned.

The customer confirmed that they filled out all the required information when processing the return.

RMA #: 200002131

Steps to reproduce

Go to the Magento Admin Panel.
Navigate to RMA.
Open an existing RMA that contains multiple orders. In our situation RMA #: 200002131
Check the “Items for order” sections.
Observe that product information is missing for most orders.

Expected result

All orders listed in the RMA should display complete product information, including the returned product details for each order.

Each order should clearly show which product(s) were returned, along with the corresponding return information.

Actual result

Multiple orders are displayed in the RMA, but product information is missing for most of them. Only one product is shown, while the remaining orders do not display any associated returned product details.

Additional information

A screenshot has been attached showing that multiple orders are listed under the RMA, but product information is missing for most of them. Only one product is displayed, while the rest have no associated product details.

The issue was observed in the Magento admin panel during return processing.

Release note

Fixed an issue where product information was missing for some orders in the RMA view, causing returned items to not be displayed correctly.

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @warehouseg-sp. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[github-jira-sync-bot]

❌ You don't have permission to export this issue.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @warehouseg-sp,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest magento instance and we are not able to reproduce the issue.Please refer the screenshot.

Could you please try to reproduce the issue in Latest magento instance and looks you were using third party modules and it may possible it is causing this issue.

Thanks.