I want the document updates to roll up to the parent task / issue and the project. Currently you have to find the correct document to find a particular comment. You can't just look at the project as a whole to find comments made on a document.
Agree. It is confusing for a user when they expect to see comments/updates at the Project or Task level and they don't, when they are trying to see where the Document comments are.
Agree. This has posed challenging for my company & partnering vendors/Agencies. Including the document level comments under the Parent Task would save time and avoid oversights.
I'm a little mixed on this one because proof comments show up in Document updates, and we have upwards of 150 Proof comments per document. It can be a bear to wade through these if they roll up! Is there some way to define Proof comments as a system-generated update so my users can filter those out if they want to find actual non-Proof updates? :)
In case the product team is still looking at feedback for this idea, I'd like to put my 2 cents in on what this should have and look like.
I've created a report that actually incorporates all updates including document updates and put it in a dashboard. What helped is it's easily identifiable that the update was made against a document (highlight it!) and identify/link to the document where that update was made to. You can imagine two similar update that said, "please have a look at this document" made to two different documents, there's going to be confusion on which document was being talked about.
Also, please sort it by entry date with the latest conversation appearing first and grouped by the thread. Currently, a thread started two months ago and recently updated will still appear at the bottom, making it harder for the user to find.
We desperately need this feature. Our design team is having to dig through proofs to find comments. There aren't any notifications when a comment is made nor are the comments rolled up. Our designers have to dig through documents to look for new comments.
