Shipping method values becomes zero when apply a cart price rule in checkout

[sheyan-ascentic]

Preconditions (*)

1. Magento 2.2.5

Steps to reproduce (*)

1. Enable Free shipping, table rates and flat rates from admin->configurations ->shipping methods.
2. Create a Cart price rule to discount a specific shipping amount.
   Marketing -> Cart price rule.

https://user-images.githubusercontent.com/34059011/54592574-abb43b00-4a52-11e9-8f32-5b32957a377a.png
https://user-images.githubusercontent.com/34059011/54592624-c71f4600-4a52-11e9-8b64-59ba1070725a.png
https://user-images.githubusercontent.com/34059011/54592662-dbfbd980-4a52-11e9-9f2c-d17e24ee6cc9.png
https://user-images.githubusercontent.com/34059011/54592686-e61dd800-4a52-11e9-9776-65881fabdd3c.png

1. Apply the discount code by selecting the flat rate from the checkout shipping methods
2. Go to home page and come back to the checkout page

Expected result (*)

1. After going to the homepage and come to Checkout flat rate shipping method should be 0 but table rate shipping method should be a value set in the table rate matrix.

Actual result (*)

1. After going to the homepage and come to Checkout flat rate shipping method is 0 and table rate shipping method also became 0 .
   https://user-images.githubusercontent.com/34059011/54593111-c89d3e00-4a53-11e9-84de-a475f6597a3e.png

[magento-engcom-team]

Hi @sheyan-ascentic. 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 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[sheyan-ascentic]

@magento-engcom-team give me 2.2.5 instance

[magento-engcom-team]

Hi @sheyan-ascentic. Thank you for your request. I'm working on Magento 2.2.5 instance for you

[magento-engcom-team]

Hi @sheyan-ascentic, here is your Magento instance.
Admin access: https://i-21832-2-2-5.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sheyan-ascentic]

Configurations done on the instance. Select country as Australia as it is configured in the table rates matrix. Other details mentioned as steps to reproduce section above.

[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

• Next steps are available in case you are a member of Community Maintainers.

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

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

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98792, MAGETWO-98793 were created

Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.