For me, an untriaged ticket has the lowest prio but when sorting by priority, it shows the "Need Triage" tickets first.
Most of my "Needs Triage" tickets are people randomly putting things (it's really like a wishlist), if something is really urgent it's either marked with "Unbreak Now" (99% of the time) or people spam everybody with it.
I understand that your point is that if a very important ticket is filled but without a prio, it's gonna be down in the list. But in practice, it's not what's happening in the few phabricator instances I've seen. If people use the priority feature, they are gonna use "Unbreak Now", if they don't, there's "Need Triage" is a mess.
Even this instance of phabricator, just looks at your tasks, lot of very low prio issues being put at the top of your list. (https://secure.phabricator.com/maniphest/query/.ee_vpVr7rr./#R)
But, I see how you want all the "new issues" to be at the top, so you don't miss a good one.
EDIT: "Unbreak Now" is already higher than "Needs Triage", I was thinking more about "High" instead.
EDIT2: ok, I would put "Needs Triage" just between "Normal" and "Low" but that seems arbitrary
Most of my "Needs Triage" tickets are people randomly putting things
Most is the key word here. Either all your customers are perfect and know how to properly assign priority for your product, or everything that comes in blindly needs triage. The word triage means to assign a degree of urgency, like a triage nurse at the ER. They have to figure out how urgent each request is and make the broken arm wait while the person with the severed limb gets treated immediately.
We personally use "Needs Triage" as a holding pen for tasks that have not been accepted onto our roadmap. We could create another priority for this, but our system works for us. The reason you don't see important tasks on there for us is we've already seen to all the severed limbs so to speak.
You can change maniphest.priorities to whatever your company specifically needs.
I'm just an end user. But I fully agree with that. Using a priority to set a status always confused me. In JIRA it works more intuitive. A task starts in the backlog, and when touched it will be pushed to status open. When somebody accepts and starts the task, it will be moved into "In progress". And the priority can be from low to high. I like Phabricator very much, but in JIRA the Boards with ranking (ranking is not a priority) you actually can set the order of the tasks in a priority group.
I think that's possible in Phabricator's workboards, too? I can set a workboard to be sorted by priority, but then I can still drag tasks around to change their order within the column. (But if I drag a High priority task to below a Normal priority task, Phabricator automatically changes it to Normal priority.)