Many people I speak to would prefer system updates turn off as default due to the excessive amount of reporting clutter it adds - some useful some not. Toggling it to the off position so people could turn it on would be more beneficial.
I agree with this except... we track custom events back into the update feed - i.e. if a custom form is updated the updates get pushed back out into the update feed and I'd hate for users to miss that. Could we potentially make this admin controllable in that admins can determine what is turned on / off in the system updates by user tier?
The functionality shouldn't change - admins should be able to turn the VIEW of it off at the Company/enterprise level. My users can't believe that they have to turn it off on every single task and issue in every single project. And we can't help them!
Lillian, that behavior sounds a bit off. In my comment above I was just referring to the default state. In our environment once a user turns it off it remains off for all projects and tasks until the user hits the switch again. I was asking that the default state for new users be set to off. If your users have to turn off everytime I think something is wrong.
