-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RestAPI add order comment without providing status sets status to NULL, preventing from showing in order grid #34180
Comments
Occurs because $this->setStatus($history->getStatus()); I would create a PR to fix this but a decision needs to be made whether to either:
|
Hi @engcom-November. Thank you for working on this issue.
|
✅ Jira issue https://jira.corp.magento.com/browse/AC-1342 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
Assign to me |
Assign to me |
@magento assign this to me |
@magento I'm working on this |
@yogesh-valiya @koushikch7 Thank you! |
I'm just repeating myself as this comment on 😞 - #36800 (comment) When I started working on this issue, the issue wasn't assigned to anyone. If the internal team was addressing the issue, may I inquire as to why it had not been assigned to someone specifically? It's frequent, where an individual is working on a particular issue and raises a pull request, only to find out that there is already a pull request from the internal team in progress. In light of this, I question the value of the effort put forth to resolve the issue. Could you clarify why the pull request is not linked to the issue if it is already in progress? |
I see your concern yogesh, Internal Team make sure to change status as per need, In this issue You will find above changes as PR:created by JIra-Sync_bot before you have tried to assign the same to yourself. |
Hello, As I can see this issue got fixed in the scope of the internal Jira ticket AC-1342 by the internal team Based on the Jira ticket, the target version is 2.4.7-beta1. Thanks |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
The text was updated successfully, but these errors were encountered: