A folder's Last Modified date does not reflect most recent update made within the folder
The "modified" date shown for a folder does not change when contents of a folder are modified. For example, I created a folder called "Project Meetings" on 21-Nov-2017. Each week, new files (or folders) are added to this folder however, the modified date of the folder has remained "21-Nov-2017", even though its contents were modified as recently as 20-Dec-2017.
This is not consistent with how Windows presents folders and their modified date. If a file within a folder was updated on 20-Dec-2017, the modified date of the folder becomes 20-Dec-2017. Teams should work the same way and be consistent with Windows.
The "Modified By" field should also update to match the most recent file (or folder) within the folder.
@microsoft - would you please comment on this? Is there a plan to have the folder modified date reflect when contents within are modified? This would avoid having to click in every time to see if there is an update. By seeing the most recent update reflected at the folder level, one can easily see which folders to open and check.
so its been 3 years and no change?
I agree with the other comments on this issue. We use modified dates to know when data has been supplied to a folder and having it as the created date rather than the modified date as it is in Windows is frustrating.
Louis van den Berg commented
I agree with the comments on this issue. I have to load reports to a folder on a daily basis. The readers of these reports check the modified date to determine if the daily reports were loaded yet. It is quite frustrating if the date is not correctly updated.
Adam Stevens commented
Adding another note of agreement. If it is useful for some people to have it the way it currently is, where the Modified date only updates if a file is added or deleted from the folder, then at least add another field option that will update when any sub-folder/file is updated.
Based on my experience, the Folder Date is the last time the "Folder" was Modified. I.E. a File/Folder was Added To or Deleted From that Folder. Modifying a File inside of a Folder does not Modify the Folder Itself, so the TimeStamp on that case should NOT be Updated/Modified.
Yes, this is a HUGE annoyance. In its current state, that column heading should read "Created Date", because that is what it seems to reflect.
Having the "Modified" date be correctly represented would dramatically improve the usability of the Files tab - especially in my current project where the file structure is enormous, it would be so much easier to traverse if we could filter on last modified reliably.
I really can't see this being that big of an ask too - kind of seems like a query just got its wires crossed.
Please please please make this right!
I agree to this point 100% based on my daily experience.
My team uses many channels and each channel have a lot of Files with Folders in it.
Colleagues updates most of the folder by creating/modifying files in it.
Hence it would be really helpful if the parent folder is up to date with the last modifies details.
Also it can help to order based on last modified folder and then access last modified files in it when larger no of folders present in a channel.
If you feel it cannot be done based on other business scenarios, then I would suggest that, if there is a indicator kind of setting, for those who need parent folder to update last modified details and for those who doesn't need parent folder to update based on whenever child files changes.
i couldn't agree more! having the folder modified date update to match the contents would make item and project status/revision tracking considerably easier. i should be able to open teams and immediately see what new files have been added/modified. as it is now i have to rely on notifications (email or verbal) from colleagues. as we are a global company this sin't a particularly smooth process