Comment 1 for bug 305656

I think this is the case were instead of saying the bug report is really a wishlist issue, we want to convert the bug into a blueprint. The problem is that the two apps are not symmetrical (as compared with bugs and answers).

I'm certain that all bugs with the wishlist classification can have a simple story behind them, but blueprints do not start with a primal use case that is judge by its merits. Instead blueprints normally start with the definition of a feature without the backing of a use case, that a stakeholder then struggles to get approved and developed.

Blueprints should be a repository of ideas; an idea may be discussed for years before there is a real need to collect implementation details.