Is status-firefoxnn overfiltered?

[Standard8]

Currently it looks like the dashboards are filtering on "status-firefox61: ?, ---", I'm wondering if that should possibly include "affected" as well, e.g. bug 1453545 was moved to the Bookmarks & History component from Untriaged, with its status flag set to "affected", however it hadn't been analysed or given a priority.

[emceeaich]

If a bug has status affected, I think it ought to have a priority and that may be another category on the set of dashboards?

[Standard8]

I think it depends on what "triaged" is defined as. If it is "someone has looked at it, possibly moved to correct location and marked when it was introduced", then that's fine.

If it is "someone has looked at it, and determined the severity/priority and if it is an important regression", then based on the example I've cited, I think that it needs "affected" to be included.

I guess it could be a different category, e.g. "Unprioritised". From my previous understanding and personal perspective as a developer triaging bugs, I was generally believing that "triaged" meant that it had been analysed and given a priority - the priority field being the major item.