@atpfm @siracusa I’m not sure how well the Chrome team holds to this (although I seem to remember that they were switching to Issue Tracker, aka Buganizer, same as the rest of Google), but normally P1 is not the highest priority a bug can be assigned, P0 is. The way it was described to me when I joined Google in 2011 was that P0 meant the world was on fire, down to P4 meaning your shoes are on fire.

P1 does become important because many teams have a policy that VPs start seeing the P0s and P1s on their metrics, so you deal with it quickly or triage to see if it can be lowered. That might have been the priority dance you saw; it was still high priority, but not something anyone wanted a VP contacting you about