Tickets sometimes get triaged by people that do not have the big picture of a particular's project member's load or goals, which leads to a bunch of tickets changed priority or triaged without actual feedback from the people that may work on them. This has happened in the past, leading to a bunch of time lost on reverting those changes and explaining why.

Technically, there is already a policy in place: https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities but that is not necessarily read before contributing to Phab (which is understandable, as most of the time discrepancies only happen by first-time contributors setting as high or UBN tickets that are affecting themselves).

While I understand that there is the need to communicate urgency by reporter in some cases, that could be achieved by a separate metric such as an "it affects me" counter that all people could use, token awards, a text description or particular tags such as "blocked-on-operations".

A technical solution maybe too complex (how to implement when several projects are involved?) or it may had unintended effects (less people participating, people joining projects/adding tags just to triage tickets), so it should be discussed. If searching for a technical solution is not adequate, this could be considered invalid/declined, but I would like to know your opinion on this.