Magento 2.3 EE : Coupon Type is not changing in salesrule table for schedule changes of cart price rules

[sneha-panchal]

Preconditions (*)

1. Magento 2.3 Enterprise

Steps to reproduce (*)

1. Create cart price rule with coupon type Auto and Action is Fixed amount discount and save.
2. Now Schedule new update in that rule and add from and to date for the rule and save that update and also save the rule.
3. Now please check salesrule table.
4. You have 3 rows added for this rule and all having coupon_type = 3 (3 is for Auto coupon type).
5. Now please edit the same rule and change coupon type "Auto" to "Specific Coupon" and save that rule.
6. Now please check salesrule table.

Expected result (*)

1. Our rule data rows in salesrule table having coupon_type = 3 will be changed to 2 (2 is for specific coupon type).

Actual result (*)

1. When i check salesrule table schedule changed data row's coupon_type is displaying 3 (3 is for Auto).
2. Scheduled changes row is not updating coupon_type in table.

Please check attached screenshots :

[magento-engcom-team]

Hi @sneha-panchal. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@sneha-panchal do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

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

Hi @sneha-panchal GitHub is intended for Magento Open Source users to report on issues related to Open Source only.
You can report Commerce-related issues in one of two ways:
You can use the Support portal associated with your account
or
If you are a Partner reporting on behalf of a merchant, use the Partner portal.