Skip to content
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

When trying to use certain multi-selects within the Magento admin for coupon report, they don't always work as intended. #36272

Closed
github-jira-sync-bot opened this issue Oct 11, 2022 · 6 comments
Assignees
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P0 This generally occurs in cases when the entire functionality is blocked. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.

Comments

@github-jira-sync-bot
Copy link

Preconditions
Install Magento 2.4 to develop with sample data.

Create 2-3 more cart rules and place an order for each.

Issue 
When trying to use certain multi-selects within the Magento admin for coupon reports, they don't always work as intended.

Steps To Reproduce

Go to Admin-> Reports > Sales > Coupons

Apply filter as below 
Date Used = Order Created
Period = Day
From = Any previous date
To = Today
Order Status = Any
Empty Rows = No
Cart Price Rule = Specified

Make sure to select a few different coupon rules

Select "Show Report"

Expected result
Display results for selected cart rule and preserve value which was selected in the multi-select box 

Actual result
The report will only return the values for the first selection from the multi-select and any additional selections will now be unselected

 

Here I have selected Test and Test2, the result shows only for test, and Test2 is unselected from multi-select.

@github-jira-sync-bot github-jira-sync-bot added Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Oct 11, 2022
@github-jira-sync-bot
Copy link
Author

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1223

@m2-assistant
Copy link

m2-assistant bot commented Oct 11, 2022

Hi @github-jira-sync-bot. 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.


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

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added this to Ready for Development in High Priority Backlog Oct 11, 2022
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in High Priority Backlog Oct 17, 2022
@github-jira-sync-bot github-jira-sync-bot added Priority: P0 This generally occurs in cases when the entire functionality is blocked. and removed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Oct 19, 2022
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in High Priority Backlog Nov 7, 2022
@engcom-Charlie
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@chittima
Copy link
Contributor

chittima commented Mar 8, 2023

Issue is fixed and here is the commit : 4670034

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P0 This generally occurs in cases when the entire functionality is blocked. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Development

Successfully merging a pull request may close this issue.

4 participants