Hi @Nuranto. 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.
⚠️ 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.

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

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

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

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

• Join Magento Community Engineering Slack and ask your questions in #github channel.

@magento give me 2.4-develop instance

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

Hi @engcom-Dash, here is your Magento Instance: https://fe74e6b08484c0858eb929e57e74a885.instances-prod.magento-community.engineering
Admin access: https://fe74e6b08484c0858eb929e57e74a885.instances-prod.magento-community.engineering/admin_f188
Login: 64dd48de
Password: 68a200a92f49

@magento give me 2.4-develop instance

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

Hi @engcom-Dash, here is your Magento Instance: https://fe74e6b08484c0858eb929e57e74a885.instances-prod.magento-community.engineering
Admin access: https://fe74e6b08484c0858eb929e57e74a885.instances-prod.magento-community.engineering/admin_058a
Login: 60dbf855
Password: 7a60f5716929

Hi @Nuranto

Thanks for reporting and collaboration.

Can you please provide detailed steps to reproduce with screenshots which would help us reproduce the issue accurately

Thanks!

(https://fe74e6b08484c0858eb929e57e74a885.instances-prod.magento-community.engineering/admin_058a/sales/order/view/order_id/3/)

Hi @Nuranto

Verified the issue in 2.4.7 and 2.4 dev instances.

But I am seeing only processing and suspend fraud options in order status after generating invoice.

Please refer to the screenshots. Let us know if we are missing anything.

I added a custom status on your temporary env.

As you can see in the code :

private function getOrderStatus(string $orderStatus, string $historyStatus): string
    {
        return ($orderStatus === Order::STATE_PROCESSING || $orderStatus === Order::STATUS_FRAUD) ? $historyStatus
            : $orderStatus;
    }

We can update status, but only if current status is processing or fraud.

Hi @Nuranto

Thanks for reporting and collaboration.

Verified the issue on magento 2.4 dev and 2.4.7 instances and the issue is reproducible. Hence, we are confirming the issue.

We are able to update the status only if the current status is in a processing or fraud state. If the status is anything other than processing or fraud state we are not able to update the status.

Please refer the attached screen recording.

We are also waiting for a patch for this issue.

I haven't seen it yet, but does 2.4.7-p2 solve this?

At least the patch was still applied by Compose.

As you can see here,
even the current 2.4 development branch doesn't have a fix yet.
https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Sales/Controller/Adminhtml/Order/AddComment.php#L94

in a quick solution for an integration here, i just removed this code from that file.

vendor/magento/module-sales/Model/Service/OrderService.php

/**
* change order status is not allowed during add comment to the order
*/
if ($statusHistory->getStatus() && $statusHistory->getStatus() != $order->getStatus()) {
throw new \Magento\Framework\Exception\LocalizedException(
__('Unable to add comment: The status "%1" is not part of the order
status history.', $statusHistory->getStatus())
);
}

Internal team is working on this issue

Any update on issue? We are using Magento 2.4.7.

The internal team already fixed this issue. Currently, in delivery queue.

The internal team already fixed this issue. Currently, in delivery queue.

So what about tagging this ticket with the milestone/release it is intended for?

The internal team already fixed this issue. Currently, in delivery queue.

So what about tagging this ticket with the milestone/release it is intended for?

we can determine relese when the code changes will be delivered, since they are in delivery process and not delivered yet we can't specify release which will contain the changes

Possibly fixed by 18dee3d?

@hostep Yes

Hi,

As per this comment #38917 (comment) we are closing this issue.

Thanks.

No milestone = release set?

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

Source: #38917 (comment)

same issue here on 2.4.7-p2

Hi @Nuranto @guilhermemap,

Thanks for reporting and collaboration.
We have re-verified the issue in Latest 2.4-develop instance , but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

1. Create a order status
2. Assign respective order status to state code processing
   
3. Place an order.
4. Create invoice. observe status is set as teststatus as it was set as default for processing.
5. Now, Change the status to processing, observe user is able to update the status successfully.

Can you please re-verify and confirm if you are still facing the issue.
Thanks.

We are still with the same issue in the 2.4.7-p2 version, via the admin page we can only change from the default processing status (processing state) once to a custom state. After this we can't change to another status in the same state, not even the default one. Also, in the complete state we can't change the status at all.
Our current solution is to use the rest api (POST in the /orders/ endpoint with entity: {entity_id, state, status}, the /orders//comments endpoint does not work to change the status in this situation).

Hi @guilhermemap ,

Thanks for reporting and collaboration.
We have re-verified the issue in 2.4.7-p3 and 2.4.8-beta1 instance. Issue is only reproducible in 2.4.7 instance and fixed in latest versions.
Can you please reverify in latest 2.4 develop or 2.4.8-beta 1 instance.

Related commits: https://github.com/search?q=repo%3Amagento%2Fmagento2+ACP2E-3178&type=commits

Thanks.

We can witness that the issue is still there in v2.4.7-p3
It applies also to Order STATE "Complete"
Waiting for 2.4.8 release, hoping that it will be fully resolved.
Status updates are a vital component of eCommerce experience.

Hi @vbidou ,

Thanks for reporting and collaboration.
We have re-verified the issue in 2.4.7-p3 and 2.4 develop instance. Issue is only reproducible in 2.4.7 instance and fixed in latest versions.
Can you please reverify in latest 2.4 develop.

Thanks.