Closed nandigowda-zz closed 3 years ago
Hi @nandigowda. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
@nandigowda do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @shikhamis11. 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).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.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- 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.
@magento give me 2.4-develop instance
Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @shikhamis11, here is your Magento instance.
Admin access: https://i-26286-2-4-develop.instances.magento-community.engineering/admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
@magento give me 2.4-develop instance
Hi @nandigowda. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @nandigowda, here is your Magento instance.
Admin access: https://i-26286-2-4-develop.instances.magento-community.engineering/admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
@magento give me 2.4-develop instance
Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-26286-2-4-develop.instances.magento-community.engineering/admin_48cf
Login: 810b7e13
Password: 73adc26fead9
Instance will be terminated in up to 3 hours.
Hi @sdzhepa. 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).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.4-develop
branchDetails
- Add the comment @magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- 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.
Hi @sdzhepa can you please check this issue with the product owner for what will be the actual result for this issue .. It seems issue for flat rate if setting is per item but it will not be issue for other custom shipping methods
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
This is still a problem on Magento 2.4. Partial invoices force-include the full order shipping amount, whereas in certain cases, the merchant may wish to invoice a lesser shipping amount.
This is still a problem in Magento 2.4.5 as well. I raised this issue with our Adobe Commerce rep and Adobe Commerce support, and they confirmed that this is expected behavior, with no plans to fix it.
*Preconditions ()**
*Steps to reproduce ()**
Place an order with 2 different simple products priced 'item 1 price' and 'item 2 price' and 'total shipping amount' flat rate shipping, that include 'item 1 shipping amount' and 'item 2 shipping amount'.
Create Partial invoice for item 1
Create Partial invoice for item 2
*Actual result ()**
Item 1 partial invoice amount is 'item 1 price' + 'item 1 shipping amount' + 'item 2 shipping amount'.
Item 2 partial invoice amount is 'item 2 price'
*Expected result ()**
Item 1 partial invoice amount should be 'item 1 price' + 'item 1 shipping amount'.
Item 2 partial invoice amount is 'item 2 price' + 'item 2 shipping amount'.