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

"Something went wrong" error is displayed when clearing the completed bulk tasks. #36255

Closed
github-jira-sync-bot opened this issue Oct 7, 2022 · 8 comments · Fixed by #36355
Assignees
Labels
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. 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

Issue:
"Something went wrong" error is displayed when clearing the completed bulk tasks.

 

Steps to reproduce:

  • Perform a bulk operation (eg: Bulk update product attributes).
  • Make the operation completed (eg: run {{{}bin/magento queue:consumer:start productactionattribute.update{}}})
  • Click on the "Dismiss All Completed Tasks" link after expanding the admin notification section.

Actual result:
"Something went wrong" error is displayed

Expected result:
The "Something went wrong" error should not be displayed while clearing the completed tasks.

Additional information:

  • Completed tasks are getting cleared regardless of the error message. This can be checked by refreshing the page or navigating to a different page in the admin.
@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 7, 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-1245

@m2-assistant
Copy link

m2-assistant bot commented Oct 7, 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

@texboy
Copy link
Contributor

texboy commented Oct 7, 2022

@magento I am working on this

@veloraven
Copy link
Contributor

Hello @texboy !

Thank you for your contribution and collaboration!

To speed up the delivery process of this fix, the internal Adobe team will take this fix in progress, complete all other work according to the Definition of Done and deliver the fix using internal workflow.

The fix for this issue will be done in the scope of the internal Jira ticket ACP2E-1245.

@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in High Priority Backlog Nov 21, 2022
@hostep
Copy link
Contributor

hostep commented Nov 21, 2022

Closed without any comments? But looks like fixed by ACP2E-1245.

@smartexcan
Copy link

smartexcan commented Nov 22, 2022

ACP2E-1245 should fix the issue, but also creates a new issue.

bulk/notification/dismiss gets sent a POST request, but the fix added the HttpGetActionInterface interface to the controller, which will likely break things

@chittima
Copy link
Contributor

New ticket was created and Internal team is actively working on it. We will provide merge commits once it is fixed.

@chittima
Copy link
Contributor

chittima commented Mar 8, 2023

Issue is fixed and here is the commit id: e76ca5a

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: P2 A defect with this priority could have functionality issues which are not to expectations. 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.

6 participants