Closed atIOCrON closed 2 months ago
Hi @atIOCrON. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:
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.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-Echo. 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:
Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.Issue: Clear Description
label to the issue by yourself.Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Hi @atIOCrON,
Thank you for reporting the issue.
We have tried this issue on Magento 2.4-dev/2.4.3-P1 and we have successfully reproduced it.
Steps followed to reproduce issue:
The invoice date filter on the Invoices page is not working as expected. Hence confirming the issue.
Thanks
:x: Something went wrong. Cannot create Jira issue.
:x: Something went wrong. Cannot create Jira issue.
:x: Something went wrong. Cannot create Jira issue.
:x: Something went wrong. Cannot create Jira issue.
:x: Something went wrong. Cannot create Jira issue.
:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2115 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @sdzhepa. Thank you for verifying the issue.
Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
This same issue was patched for the Sales > Orders grid already:
Related commit https://github.com/magento/magento2/commit/77e1e2beacbcd03da2fe612ccfdb6c0c23e00951
Is there any update on this issue? Is it going to be fixed?
Any update on this? When will it be fixed?
Hi @engcom-Echo , Is anyone working on a fix for this issue?
I can see it is tagged dev in progress but if no one is actually working on it can you remove that tag so someone else will see it and pick it up?
Hi @engcom-Echo Are you working on this issue? It's been 2 years, please remove yourself if you're not working on it.
@tuanpht Thanks for your contribution!!.
As per this comment https://github.com/magento/magento2/issues/34956#issuecomment-1016399330 we are closing this issue since issue has been fixed.
Thanks.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
This same issue was patched for the Sales > Orders grid already:
https://support.magento.com/hc/en-us/articles/4403024155917-MDVA-34330-Orders-not-filtered-according-to-admin-timezone
However, the same issue still persists for invoices, shipments and credit memos.
Severity: S1 - Affects critical data or functionality and forces users to employ a workaround