{{Done}} Silencing notifications requires real-time collaboration with someone with shell access to the Phabricator servers, but you now will have the right to prepare and run a batch of changes regardless.

@MPhamWMF: For some more context: As our code is public it can be changed and improved by anyone outside of some team in some organization. Unless stewards/maintainers of a codebase are not against implementing a Phab ticket (being against would imply "declined" task status), valid Phab tickets should remain open and be tagged with the blue codebase project tag they are about (as teams are everchanging in organizations while codebases remain). If some team does not plan to work on some valid open Phab ticket, I'd remove the (violet) team project tag.

Done. Please see https://www.mediawiki.org/wiki/Phabricator/Help#Batch_edits - thanks!