Our users like to sort by last modified date. That is almost impossible since every time a file is opened it updates the modified date whether or not anything actually changed in the file.
So they get older files at the top of the sorted list merely because someone opened the file.
It also creates an issue with tracking back changes - both because only 100 versions are kept, which are quickly chewed up by the no-change "modifications" and also makes it difficult to track what happened version to version when nothing actually happened in a version.
This creates workflow issues as well as legal implications when we cannot prove when something happened in a file.
Lynda Finley
| Categories | User Workflow |
With the release of Composer 2.0 we fixed the issue where revisions (and updates) were being created when there were no changes that were made. This is now resolved!