I use the publication report all the time. I mostly do three things with it:

1. Export all the publication objects from it, for various reasons.

2. Compare versions of a pub, mostly for translation purposes.

3. Review the status of all the objects, for various reasons.

Could you share some examples of when you would be using this report for all the above #3 use cases?

Here's the most important use case. My writer updates a publication and I want to understand what needs to be sent to the translators. I know that often there is a tiny change to a topic or library, and sometimes the changes are complex (for example, we have a product variables library that is Translation Memory un-friendly). So I look for specific objects that I know have been problematic in the past and do a compare the English against previous versions in the UI. From there, I decide whether I want to send the troublesome/important objects separately - so they get special attention - or just batch them with the rest of the project for the translators.

I realize that most localization managers do not focus this level of attention to individual objects (and we push/pull our translations manually to have more control), but I have found it to be more useful and faster than dealing with TM issues downstream.

Does this answer your question?

Hi Elizabeth, Thanks for sharing the details. 

Hi Elizabeth, Thanks for sharing the details.