tag / group / categorize object updates

There can be many reasons users and the system enter updates on an object (project, issue, task, etc). This can make finding the most relevant update for a report challenging. Today's design also assumes that every update the object owner makes is a "condition update".

We propose adding functionality to #tag, categorize, or group updates. This would support the ability to filter the updates for a more precise item - such as the last "project status summary" or the "project gate review" or "staffing" topic.

The tagging/categorization should support a single update having multiple tags - such as "customer facing update" and "internal project status summary".