Disable Comments when no one will be notified

[#1]

Problem: Updates that our clients make sometimes go into places where no one will be notified (We try to train them, but it'd be nice if we didn't have to)

Possible Solution: It'd be great for our use case if we could set either a User setting or Project setting that would be something like "Do not allow updates in places that no one will be notified" so they wouldn't be allowed to post updates if they forget to subscribe someone or if they are posting an update to a Parent task that has no one assigned to it (And no one added to the notification list)

[#2]

We are also experiencing this as well post-implementation.

Rather than disabling the ability for a user to post a comment on an unassigned task or issue, an alternative idea is that the project owner get automatically notified with the comment posted on one of their project tasks or issues. This would also be helpful when a user enters a comment on the Project > Updates page.

[#3]

It'll be beneficial if we could also have a setting that allows team members to be notified of a comment, instead of having the commenter to enter the names of the recipients.

[#4]

I agree 100% with Heather Rehm-Stelter. The solution would not be to disable comments, that is simply not functional or logical at all. The solution would be to enable a setting which, when turned on in the system, a project owner gets notified of all comments posted in the Updates tab by users, whether they are included or not in the update.

[#5]

Heather's solution is better, a combination of that with maybe an alert in the browser or something to indicate that your response isn't going to be sent to anyone would be great! My view point is that it's better for us to have no comment than to have a comment go to nobody as our customer will have an expectation of a response right now. No response looks much worse on us than a comment box that can't be filled in.

[#6]

Our problem is people post on the original object instead of the resolving object. I'd suggest that if an object is resolved by another object, then the update is copied to the resolving object.

[#7]

I have the same issue as Brian. People find the original object instead of the resolving object (generally a project). Since our workers are working on the project, they never see the original object & any comments added.