Cannot change intermediate custom status in admin using add comment form

[zakdma]

Preconditions and environment

• Magento version 2.4.7-p1 (latest)

Steps to reproduce

1. Install vanilla Magento
2. Go to admin Stores => Order Status
3. Create two statuses "Sent" and "Ready for Pickup" and bind them to "Processing" state
4. Create product and register customer
5. Place order on front using this product and customer and default shipping and payment methods
6. Go to admin Sales => Orders
7. Open previously placed order
8. Create invoice by clicking Invoice button on top
9. See order changed status to "Processing"
10. Go to "Add Comment" form change status to "Sent" and add any comment
11. Reload order form and see status changed to "Sent"
12. Go to "Add Comment" form again and change status to "Ready for Pickup" and add any comment
13. Reload order form

Expected result

See status is changed to "Ready for Pickup"

Actual result

See status is still "Sent"

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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[bot]]

Hi @zakdma. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[m2-assistant[bot]]

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: :point_down:

• [ ] 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

  - 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.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://5e5b258c627b4317f1ba746fbda8c703.instances-prod.magento-community.engineering Admin access: https://5e5b258c627b4317f1ba746fbda8c703.instances-prod.magento-community.engineering/admin_e21e Login: c76b96f0 Password: b93f2f60ca26

[engcom-Bravo]

Hi @zakdma,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the attached video.

Steps to reproduce

• Install vanilla Magento
• Go to admin Stores => Order Status
• Create two statuses "Sent" and "Ready for Pickup" and bind them to "Processing" state
• Create product and register customer
• Place order on front using this product and customer and default shipping and payment methods
• Go to admin Sales => Orders
• Open previously placed order
• Create invoice by clicking Invoice button on top
• See order changed status to "Processing"
• Go to "Add Comment" form change status to "Sent" and add any comment
• Reload order form and see status changed to "Sent"
• Go to "Add Comment" form again and change status to "Ready for Pickup" and add any comment
• Reload order form

https://github.com/user-attachments/assets/44b40e2a-9256-426d-ac9e-0ae0d43e422d

The Status is still in sent state.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12462 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[simonmaass]

does anyone know why this change was introduced in the first place?

[simonmaass]

i guess this was why: https://github.com/magento/magento2/issues/36562

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://5e5b258c627b4317f1ba746fbda8c703.instances-prod.magento-community.engineering Admin access: https://5e5b258c627b4317f1ba746fbda8c703.instances-prod.magento-community.engineering/admin_9e52 Login: 72ce59df Password: f723c7fd67d9

[hostep]

Possibly fixed by https://github.com/magento/magento2/commit/18dee3d979ed8ee68a44324e892e6b7f570c987c?

[engcom-Bravo]

@hostep Thanks for your Contribution!!.

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket ACP2E-3178 by the internal team Related commits: https://github.com/search?q=repo%3Amagento%2Fmagento2+ACP2E-3178&type=commits

Based on the Jira ticket, the target version is 2.4.8-beta1.

Thanks

[hostep]

Thanks for confirming @engcom-Bravo, can you also close https://github.com/magento/magento2/issues/38659, which is a duplicate of this issue here? Thanks!

[simonmaass]

great - so will have this fix in april 2025!