When markups/Issues are added to a file, they remain even after the file has been replaced with a newer version. This carry-over feature is not convenient when markups/Issues are used to indicate comments on the file. Typically, when a comment is added, it is expected that the file will be revised offline and re-uploaded with the same file name.
Due to the current behavior, once the file is replaced with a newer version, the markups/Issues from the previous version may become misaligned on the newer version, especially if the file has undergone upscaling, downscaling or rearrangement.
While the carry-over function is intended to facilitate the review process by allowing reviewers to quickly check whether previous comments have been addressed, it is only effective for submissions that require minimal revisions. When major changes are made to the file, the carried-over markups/Issues may appear scattered or out of context.
If there were an option to disable this carry-over feature, it would be beneficial to also have the ability to view each version of the file with only the markups/Issues made on that specific version, enabling clearer comparison and review.
Our current workaround to prevent this issue is to avoid using the auto-versioning feature when uploading revised files. Instead, we include the revision number in the file name to ensure the new file does not overwrite the previous version and carry over all markups/Issues. However, this approach is not preferable, as it results in more files appearing in the folder, and the files are not linked to each other, even though they are the same document with different revisions.
