This task was an outcome of the https://wikitech.wikimedia.org/wiki/Incident_documentation/20160712-EchoCentralAuth incident
Retro notes: https://wikitech.wikimedia.org/wiki/Incident_documentation/20160712-EchoCentralAuth/Retrospective
One suggestion was for me (@greg) to do a weekly review of all UBN! tasks in hopes that I can identify 'true' UBN! issues and correctly action (sic) on them quickly. To that end I have scheduled a 30 minute block in my calendar at 10:30am Pacific (17:30 UTC, during this current daylight savings period).
I believe though, if this is to have a chance, this triage should be a public one with, for instance, a Phabricator event with associated IRC channel where at least I think out loud (in text) as I review the list of UBN!s.
As I/we review those tasks, however, we'll need a consistent criteria by which to judge them and action (sic) on them. That is where this task is important. I/we will need to be able to review those UBN! tasks and either:
# Identify them as, yes, UBRTFN! and assign a "first responder" (see: T141066)/follow-up appropriately (and quickly)
# Identify them as not UBRTFN! and either:
## Reduce their priority to 'High' or lower, or
## Keep them at UBN! since UBN! is not special in our Phabricator instance (NB: And, implicitly this means a higher cognitive load on Greg/us as some UBN! tasks will sit that way for a while yet be not actionable in the same way)
NOTE: We need to resolve T140207 to choose between A or B :)
Also, if the above triage turns out to be useful it will probably become one of the standard duties of that week's MW Train deployer (a duty that is rotated, every two weeks, within the Release Engineering team).
See also: {T141066}