The 'blocking‑aviary2.0' flag is now 'blocking‑aviary2' donno if this was changed on purpose but I only noticed this after the bugzilla 2.20 upgrade.
I think this is a side-effect of the "force UTF8 on new bug entry" hack that I used to have in place being removed. The intent was to go UTF8 site-wide instead of just on the bug entry page, but I didn't get the necessary tools working in time to pull it off. The short-term hack will probably go back in tomorrow.
Ignore comment 1, I think I misinterpreted this bug originally because the encoding got messed up when you submitted it. There is no anything-aviary2 flags at all, and based on other flag names (blocking-firefox2, etc) I suspect this was done on purpose by one of the admins. I don't think this was an upgrade regression, just lucky timing.
as far as we know, this was intentional.
It was indeed intentional.