Hi Jamie, Although "Updates" can not be reported upon (or filtered) natively, the "Notes" object can do both, and is likely to contain the same human-entered information you're after (in the "Note Text", as opposed to the "Audit Text", which is for system-generated information such as status changes, etc.). So although there is no way to extend the current functionality of the Updates dialog you've shown, what you might consider is adopting a "prefix" convention to tag those Updates that you'd later like to filter and retrieve via a Notes report. For best results, I'd suggest a adopting a non-typical pattern to avoid false positives on filtering (e.g. "Note Text CONTAINS ~TODO~ etc.). Here's a few examples:
~TODO~ Make sure we come remember to...
~BEST~ For the lookback, this illustrated the Best Practice of...
~OOPS~ Next time we run into this, we should avoid...
etc.
A few years ago, I took this concept even further (perhaps a bridge worth, some would say), and paired such conventions with special calculated parameters that examined the Last Update (through which each Update passes, in turn) that each "watched" for certain prefixes, and upon finding an entry that matched, then appended the value to an ever-growing "targeted audit" text area. Doing so neatly collected all of those related items in a single, project custom parameter that could then be easily reported (e.g. viewed across multiple Projects in a grid) using built in reporting. Regards, Doug Doug Den Hoed - AtAppStore
