To be clear, both RejectedBlockers (33-beta and 33-final) shouldn't be displayed (or I'm misunderstanding something).

@lbrabec talked to me about this and I already managed to forget half of it. But the basic issue seems to be that whenever a bug is proposed against some blocker milestone and then the milestone gets removed, that bug proposal is marked as rejected (even though there doesn't have to be a RejectedBlocker in the Whiteboard). I'm not sure whether this is a bug or intentional and why. But that's how BBA is currently implemented. And the discussion code then inherits this.

In order to fix this, we need to look at why BBA behaves the way it does (that only amplifies the need to document your code, let's see if we did that or not), and possibly fix a bug (looking into the Whiteboard) or say this is how we want this (I'm not convinced at this moment).