Hi Kelly, I have a theory on Notes vs Updates. I might be wrong. But I have a large coffee and some time. So I'll try to make it interesting. (Lower the lights, and imagine a campfire with a tom-tom thrumming softly in the background...) Back in the day, pre-Anaconda, when dinosaurs (like me) roamed the plains, AtTask's [sic] auditing model was primarily composed of four checkboxes at the template and project level. When all such boxes were checked off, it effectively told Workfront to record every change as a Note (e.g. "Doug changed the Status from NEW to CUR", "Doug changed Planned Start Date from Jan 8, 2005 to Jan 12, 2005", etc.). In the Beginning, this Was Good: for Workfront Customers with a need for full auditability (e.g. SOX compliance, Safety Requirements, Costly Schedule Changing, etc.) this behavior gave them the coverage and confidence they needed, in a reliable and reportable object they could access Рnamely, a Notes report. However, for those running the datacenter and watching this ever escalating volume of important but static audit information, I suspect it became a Bad Thing: lots of disk, lots of data, lots of trouble brewing on the evolutionary horizon. Enter the dawn of Anaconda, and Workfront's pivotal move to branch the auditability timeline with the New Security Model, which among other things introduced the JOURNAL object, which drives the Updates tab we're now familiar with. The premise of this New Way was that those who needed auditability could opt in via the Update From Feed dialog, picking and choosing ( only , as would also now be a Reasonable Limit) the most important fields to audit, and in turn, tracking that information in the Updates Tab. And after a few releases, removed the checkboxes from the user interface, and defaulted them to "off". Legend tells of a group of elders who Рat the time Рintended to observe the usage of the New Way, and then if warranted, to expose JOURNAL in the same way as NOTES for reporting. But that group has now moved on. And since that reporting option has not yet come to pass, I can only conclude that it has simply never become important enough for anyone to address (including me). Perhaps some of the more recent sightings of Updates "falling off" the Updates Tab will spark interest in this area again. Stepping back again to Pre-Anaconda...at the time, the four checkboxes were so valued that we created our Audit Level: Issues, Projects and Tasks solutions, which allowed users to filter (typically for all) objects and quickly turn on (typically all) the checkboxes to ensure that the desired auditability was always on. And although little remains of those solutions other than some cave drawings (translation: we've delisted them, and they are now only available privately), I have observed that for customers of a Certain Vintage who continue to use Projects that did have those checkboxes on, their Notes cornucopia floweth over; where, contrarily, those Projects created after that critical timeline event seem to lack such Note information. With all these stories in mind, the fact that You see what you do, but Others do not might be due to the Vintage of the Projects, and the presence or lack of that critical four checkbox strand of residual AtTask DNA. (drumming stops). Regards, Doug ------Original Message------ Thanks for sharing the info....it is interesting though that my Note report shows status changes and general edits.¬† I rely on my Note report more than my Update tab for research, etc when trying to identify when some of my fields changed, etc.¬† I have found the Note report to be more reliable than¬† the Update tab.¬† For example, I opened a ticket with Workfront where edits I know I made to specific items were not displaying in the Update tab for a few items, but were displaying on others for the same day, time, etc.¬† In both instances, the edits were in my Notes Report.¬† Workfront is still looking into this issue. To make it even more interesting, in doing some follow up work on my ticket a couple of weeks ago, I noticed that new screen shots that I took of the Update tab, for the same items that I had screenshots for when I opened the ticket, additional items were no longer displaying in that update tab.¬† However, the Notes report still showed everything.¬† So not sure why my Notes report seems to be working for me and is more reliable than the Update tab.¬† There are other threads in the community where we were discussing similar things and it seems to be a little different for different users; not sure why.¬† At the end of the day, this needs to be accurate and reliable reportable. At Leap last year, I talked to a few people in the Experience Zone about even providing and additional filter option on the Update Tab to filter to include System Updates, that exclude the Hours Entry records.¬† This would make it quicker and easier on the eyes.¬† That, plus having the ability to automatically expand in instances of "other updates" that occur. Here are screenshots from my report.¬† I modified my filter in my Notes report to pull anything where the Audit Text field contains "Live".¬† The report shows qualifying items that are custom fields and status field.¬† Admin Kelly-Wehrmann SSFCU
