magento2
magento2 copied to clipboard
Orders page - Filtering with Purchase Date is not working when removed and re-applied
Preconditions (*)
- Magento 2.4-develop having Orders
Steps to reproduce (*)
- Admin - Sales - Orders
- Filters - Purchase Date - Select from and To date
- Apply Filter - No Issue. Filter applied
- Remove/Close the Filter
- Click again on Filters
- Previous filter dates are displayed and apply same filters - Issue. Filter not working Issue also observed when only To Date is changed and filter applied. Filter not working properly.
Expected result (*)
- [Screenshots, logs or description]
Actual result (*)
Attached Video for reference
- [Screenshots, log b92b71bc-9999-40e0-9595-00e1420a4554 (1).zip s or description]
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- [ ] 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”.
Hi @engcom-November. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:
- Summary of the issue
- Information on your environment
- Steps to reproduce
- Expected and actual results
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-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: :point_down:
-
[ ] 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 labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears. -
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself. -
[ ] 3. Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to. -
[ ] 4. Verify that the issue is reproducible on
2.4-developbranchDetails
- Add the comment@magento give me 2.4-develop instanceto deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-developbranch, please, add the labelReproduced 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: Confirmedonce verification is complete. -
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-2094 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
@engcom-November We will reverify this ticket. Hence moving it to the Ready for confirmation board.
Hi @engcom-Hotel. 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).
Details
If the issue has a valid description, the labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears. -
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself. -
[ ] 3. Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to. -
[ ] 4. Verify that the issue is reproducible on
2.4-developbranchDetails
- Add the comment@magento give me 2.4-develop instanceto deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-developbranch, please, add the labelReproduced 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: Confirmedonce verification is complete. -
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
Hello @engcom-November,
Thanks for posting the issue!
We have tried to reproduce the issue in Magento 2.4-develop and it is reproducible for us with the mentioned steps.
We have followed below steps:
- Go to the order page (Admin panel)
- Filter orders using Purchase date (Working fine):

- Now clear the filter by clicking the cross(x) button near the purchase date filter.
- And then open filter box, purchase from and to date are still there in the textbox, click on
Apply filterbutton, instead of filtered dates, all orders listed in the grid(not working fine):
Hence confirming this issue.
Thanks
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-2094
@engcom-Hotel Is there an update on this issue? Still seeing this in Magento 2.4.4-p2.
Hello @ksenia-zlotin,
Thanks for asking for the updates!
As I can see the JIRA status of this issue, is still in the implementation phase. As per the process, someone from internal will pick this issue and raise a PR to fix this.
The issue can also be picked by the community as well to open up a public PR, we will process them as well.
Thanks
@engcom-Hotel This is still happening in Adobe Commerce 2.4.4-p6. Is there a patch provided for this issue? Just looking for an update on this issue, thanks!
Hi @engcom-November,
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the attached video.
Steps to reproduce
- Admin - Sales - Orders
- Filters - Purchase Date - Select from and To date
- Apply Filter - No Issue. Filter applied
- Remove/Close the Filter
- Click again on Filters
- Previous filter dates are displayed and apply same filters - Issue. Filter not working
- Issue also observed when only To Date is changed and filter applied. Filter not working properly.
Screencast from 11-01-24 11:56:10 AM IST.webm
Previous filter dates are not displayed after removing filters hence issue is not at all reproducible in Magento 2.4-develop instance,
It might be possible issue has been resolved in Latest branch and it is recommended to verify the issues in Magento 2.4-develop branch.Could you please upgrade the Magento to the Lastest version.
Hence We are closing this issue.
Thanks.