This is related to D691#13273. This basically joins //Particular taskotron task// rule (with hardcoded outcome) with #671 rule. The reason is that in FMN you can't define logical OR between rules. So if you wanted to have this very common use case, you would have to define two different filters. I'd like to make it easier through this tailored rule, which can be then used in a default filter enabled for all our users.

Let's name the rule e.g. //Taskotron task failed or changed outcome// and describe it as a handy way of filtering a very useful use case - being notified when either check failed for an item (a build, an update, etc), or the item was fixed and the check now passes (i.e. changed outcome).

Hint: Our FMN rules are here:
https://github.com/fedora-infra/fmn.rules/blob/develop/fmn/rules/taskotron.py