An error occurred while saving the commentJim Ryan commented
I would bet that they don't even consider this a problem. Some engineer somewhere probably said "Well, the file is a new file to OneDrive, so the created date and modified date should be the same as if creating a new file." As is typical for Microsoft, they don't consider users real-life use cases.
When I copy a file from one hard drive to another locally, the modified date is preserved, so why should it be different because the drive is in the cloud?
Also, many users find files by sorting in chronological order. It is an incredibly common use case. The current OneDrive implementation makes this impossible. My company will not move to OneDrive (we're sticking with Google Drive) until this is fixed. It's unfortunate, since we'd love to take advantage of the version tracking and collaboration features of OneDrive + Office 365, but we can't.Jim Ryan supported this idea ·