Seems useful for any implementation of an activity stream. Create opportunities to engage with the content where ever it is visible. Excellent call out. At the very least, put a reply button, yet opening an editor right on the stream would be ideal that then took you to the new reply at wherever the context was (i.e. your reply's position in the thread).
Not only when fixes go live, but what issues exist. We need to know:
That IPS is aware of an issue that happens in <x> circumstances
That an administrator can take <y> action to workaround the issue until a fix is in place (disable a thing, not use a thing, configure a thing a certain way, etc.)
That the issue is being addressed by the IPS team
That a resolution to the issue is expected/will be available/is now available with <z> release/patch
As an example, we are testing an upgrade to PHP8. You announced that something involving PHP8 has been resolved, which then informed me of items 1, 2 (don't use PHP8 yet), and 3. I don't know 4.
Being able to go to a "status page" of known issues (i.e. bug tracker, but not like the bug tracker that gets turned on in beta releases), and see what known issues exist, if there are any workarounds, and when a fix might be put in place (think knowledge base), would help drive self-service engagement with support issues and help people like me know what issues are already known and when to expect a resolution (or how I can work around it).