Bulk Action Logs in backend missing if integration_id != user_id

[WalterNu]

Preconditions (*)

1. Magento Commerce 2.3.2

Steps to reproduce (*)

1. Create an integration for REST API usage
2. Do a bulk product update or any other bulk action
3. Check the "Bulk Actions" page in magento backend

Expected result (*)

1. Log entries are in db table magento_bulk
2. Log entries show up in backend

Actual result (*)

1. Log entries are in db table magento_bulk
2. Log entries don't show up in backend

In Database everything looks fine.

But in Magento Backend the Bulk Action Log entries just show up, if the integration_id of the used api matches the current backend user_id.
-> If i update the column user_id in table magento_bulk to the id of my current magento admin user id the entries are shown correctly.

[m2-assistant]

Hi @WalterNu. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@WalterNu do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Delta. 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: 👇

• 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 label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[m2-assistant]

Hi @engcom-Golf. 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: 👇

• 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 label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Golf]

HI @WalterNu thank you for you report, this is expected beheavior, there is a method to check for user id, i'm closing this as non-issue.

[WalterNu]

Yes there is a method. And this method is wrong.
In my case a external seo consultant with restricted backend access sees all bulk action logs, but I as a admin shall not be allowed to see it? In my view I don't expect this behaviour.

[engcom-Golf]

@WalterNu I think that this behavior is correct, you can open an issue here -> https://github.com/magento/community-features/issues and discuss this feature.
Bulk Actions displayed for a user who has created an integration for this, so if your SEO have permission to create an integration this will be visible only for him