(Lack of) Integration between Blueprints & Bugs

[Steve McInerney]

Probably more of an addition to the wish list to drown beuno under. ;-)

Problem:
Creating a blueprint. Want to 'link a bug to this blueprint'.
Have to copy'n'paste the bugid into the form.

Would prefer a more clicky less arduous method.
ie get taken to some simple search mechanism; select the bug(s) I want; and have them automatically added.

I suppose, in much the same way that a shopping cart on a well built site works. They recall where you were; what you're trying to achieve; and help you get there.

While the above is specific to Blueprints to Bugs; the same logic flow could be used in a number of places.

[Curtis Hovey (sinzui)]

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.