Better organization/segregation of wishlist items (enhancements/features)

[Bryce Harrington]

When Inkscape was using SourceForge, we had separate trackers for feature requests (and for patches). When we converted to Launchpad, all of these got imported into the same Launchpad bug tracker. In general merging these together is working out okay, but due to the large number of feature requests we had, it's bloated up our bug database quite a bit.

In Launchpad, Wishlisted items cannot be prioritized, as we'd done in SourceForge, so it's hard to distinguish which are key feature needs, and which are just "nice to have".

For tracking purposes, it would be nice to separate out the Wishlist bug counts from the general Open bug counts, since they're not really bugs, and instead list them as their own category.

[Przemek K. (azrael)]

What about Launchpad Blueprints? Maybe you could use it for this purpose?

[Matthew Paul Thomas (mpt)]

Perhaps you could use a "feature" or "rfe" tag, and pretend that the "Wishlist" importance level doesn't exist? Then you could give feature requests importance levels just the same as bugs. You could also search for bug reports that do/don't include the tag.

[Stephen Eaton (seaton)]

I would also like to see a count of wish-list items added to the status portlet, preferably separated from the open bug count.

[Rasmus Eneman (pie-or-paj)]

Actually I think it handles it pretty good right now. Just tag it with "feature request" or
something. Bugs and feature request is basically the same, with priorities, assignments,
status, milestone and stuff. Personally I think of "wishlist" as just another priority, bugs
with lower priority than low could be wishlist too.

The only thing I would like to change is the word "bug" to something more generic,
Google Code uses "issue" wish is better but still not perfect.