Will an upgrade to 2.1.10 solve the known Personalised Product SKU bug?

[Ben_Uren]

Hi

We are in the final stages of having a Magento website built and integrated with our back office system. We have encountered a problem which is a notified bug in Magento and need to establish if an upgrade to 2.1.10 will resolve or if there is another way to get around the issue - http://devdocs.magento.com/guides/v2.1/release-notes/ReleaseNotes2.1.10CE.html

BUG

Custom options are given a different id in the Magento database every time the product record is saved. This means that if a product record gets saved after a personalised order has been placed then the custom option referenced in the order record no longer exists with that ID so we can’t look up the option SKU from the product. See https://github.com/magento/magento2/issues/5931

Thanks you for your help.

[Tom Robertshaw · Accepted solution]

I can't say for sure but it does look like it from what they've said. 

In the release notes is the line:

"Magento now correctly displays custom options at the store-view level. GitHub-2908, GitHub-5885, GitHub-5612 "

While this line doesn't mention the exact github issue you link to, the one you link to has this comment: https://github.com/magento/magento2/issues/5931#issuecomment-238185369

"@mktudock thank you for your report.

We already have internal ticket for this issue: MAGETWO-56411
Created for GitHub issue #5612
I have linked it to this issue as well."

And the release notes for 2.1.10 do mention issue 5610 being resolved by this release.