[Issue] Ensure that invoice comments are returned when requested by GraphQL queries

[m2-assistant]

This issue is automatically created based on existing pull request: #31606: Ensure that invoice comments are returned when requested by GraphQL queries

---

Description (*)

As part of the GraphQL schema for customer orders, invoices can be requested, along with their comments. However, the current implementation does not return any comments for invoices, resulting in a null value always.
This pull request ensures that invoice comments (that are visible in the front-end) are returned when requested in the query.

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

1. Create a customer order and an associated invoice.
2. Add a number of comments to an order invoice, including both visible and not visible in the front-end.
3. Call the customer GraphQL query, requesting orders, invoices and their associated comments - e.g:

query {
    customer {
        orders(filter: { number: { eq: "000000154" } }) {
            items {
                invoices {
                    comments {
                        message
                        timestamp
                    }
                    items {
                        product_name
                    }
                }
            }
        }
    }
}

Expected result:
Invoice comments are retrieved in the graphql response

Actual result:
Invoice comments are not retrieved in the graphql response.

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)

[GovindaSharma]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @GovindaSharma. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @GovindaSharma, here is your Magento Instance: https://1a50348b5bdaf0f2c19b76bee8bfa713-2-4-develop.instances.magento-community.engineering
Admin access: https://1a50348b5bdaf0f2c19b76bee8bfa713-2-4-develop.instances.magento-community.engineering/admin_be8d
Login: 5f710c6a
Password: 54f9182161b5

[aligent-lturner]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @aligent-lturner. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @aligent-lturner, here is your Magento Instance: https://1a50348b5bdaf0f2c19b76bee8bfa713-2-4-develop.instances.magento-community.engineering
Admin access: https://1a50348b5bdaf0f2c19b76bee8bfa713-2-4-develop.instances.magento-community.engineering/admin_ccff
Login: 56a3af38
Password: a0f7eaf7e47b

[m2-assistant]

Hi @engcom-November. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.