
1- in app/code/Magento/Sales/view/frontend/templates/email/shipment/track.phtml
<?php $_shipment = $block->getShipment() ?>
// my fix
<?php $_shipment->getTracksCollection()->addFieldToFilter('parent_id',array('eq' =>$_shipment->getId())); ?>
$convertOrder = $objectManager->create('Magento\Sales\Model\Convert\Order');
$shipment = $convertOrder->toShipment($order);
// fix the issue after convert get all shipment trackers
$shipment->getTracksCollection()->addFieldToFilter('parent_id',array('eq' =>$shipment->getId()));
Hi @aldf. 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-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.
@aldf do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@magento-engcom-team give me 2.3-develop instance
Hi @aldf. Thank you for your request. I'm working on Magento 2.3-develop instance for you
Hi @aldf, here is your Magento instance.
Admin access: https://i-19887-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.
i created test order
I didn't receive the email
so I can't use this is instance
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: :point_down:
Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.[x] 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.
[x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[x] 4. Verify that the issue is reproducible on 2.3-develop branchDetails
- 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
[x] 6. Add label Issue: Confirmed once verification is complete.
[x] 7. Make sure that automatic system confirms that report has been added to the backlog.
@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97260 were created
Hi @Nazar65. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:
Component: XXXXX label(s) to the ticket, indicating the components it may be related to.[x] 2. Verify that the issue is reproducible on 2.3-develop branchDetails
- 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_!
[ ] 3. 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
[ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.
I'm will work on this
Hi @aldf. Thank you for your report.
The issue has been fixed in magento/magento2#19981 by @Nazar65 in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming 2.3.1 release.
Hi @aldf. Thank you for your report.
The issue has been fixed in magento/magento2#20184 by @mage2pratik in 2.2-develop branch
Related commit(s):
The fix will be available with the upcoming 2.2.8 release.
I think you should reopen this issue, because aldf wrote:
also if the order converted to shipment MagentoSalesModelConvertOrder->toShipment($order);
then $shipment->getAllTracks() will return all trackers
and this is still true in 2.2.11: if you get all tracks using converter, you get a result (all tracks for all orders), but if you use method getTracksCollection on order, you get a differente result (just one track, and this is correct).
Here are the steps to reproduce:

I think that the fix provided with commit f8df2dfd8a99202b52480428618f4c33966a7ba1 is just a workaround in the phtml. But if you use $shipment->getAllTracks() in other places in your code, you still get the issue.
Most helpful comment
I think you should reopen this issue, because aldf wrote:
and this is still true in 2.2.11: if you get all tracks using converter, you get a result (all tracks for all orders), but if you use method getTracksCollection on order, you get a differente result (just one track, and this is correct).

Here are the steps to reproduce:
I think that the fix provided with commit f8df2dfd8a99202b52480428618f4c33966a7ba1 is just a workaround in the phtml. But if you use $shipment->getAllTracks() in other places in your code, you still get the issue.