Category tree in Cart Price Rules is not rendered correctly

[annukka-tormala]

Preconditions and environment

Magento version 2.4.7-p1

Steps to reproduce

1. Navigate to Cart Price Rules from admin (Marketing > Promotions > Cart Price Rules > [some rule] )
2. Go to Actions tab and apply category rule (Actions > Apply the rule only to cart items matching the following conditions > Select category)

Expected result

All the subcategories should be visible in the category tree.

Actual result

Only categories 3 levels deep are rendered.

Screenshot from category tree from Cart Price Rules condition:

Screenshot from the category tree from Catalog>Inventory>Categories from admin: As you can see, all the subcategories are rendered here, but not in the Cart Price Rules condition category tree

Additional information

This seems to have happened in 2.4.7 when the extjs library was replaced with the latest version of jsTree. Related commit: https://github.com/magento/magento2/commit/4bfcc46c542101ecbd96ea1baff5a540b71b17bc#diff-64ae3799eb8d244fd03f20f4ea01674fdab57167f773924837a36871311d2985

Note: similar issue in categories was fixed earlier: https://github.com/magento/magento2/issues/38851#issuecomment-2345340785

Release note

No response

Triage and priority

• [ ] 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.
• [X] 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”.

[m2-assistant[bot]]

Hi @annukka-tormala. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• 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.

[hostep]

No idea if the category tree widget is used by price rules, but if it does, maybe https://github.com/magento/magento2/issues/39008#issuecomment-2427670552 fixes your issue?

[annukka-tormala]

No idea if the category tree widget is used by price rules, but if it does, maybe #39008 (comment) fixes your issue?

Unfortunately no, that widget category tree template is not used by the price rules.

[m2-assistant[bot]]

Hi @engcom-Bravo. 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).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced 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: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.