Comment 4 for bug 215070

Actually, this is not really a problem that needs to be solved, but rather an improved functionality.

The goal is to enable teams to label bug reports in a more structured manner, by enhancing/extending the options given by the generic and built-in "Status" information.

You refer to the "bugtag" tag in your post, but without knowing that this is indeed actively used to classify certain bug reports, it is useless. However, if I could choose "bugtag" as a possible search term in to "Launchpad Bugs" I might have decided to have a look.

Reading the list of bug reports tagged with "bugtag" that you refer to, it is clear that several users ask for a more structured and customizable way to use tags. I originally suggested a "group" field, but that same functionality could just as well be implemented on top of the tag system.

So, to illustrate the point -- but not to advocate one particular implementation -- I imagine the following scenario:

A team owner -- or even any user -- is allowed to select a limited number of tags -- private to that team (or user). These labels/tags appear in a combo-box next to the Status, Milestone and Importance fields, and members of the team can select one (perhaps several) of them. This enables the team to define and make use of a workflow most suitable for that team.

By providing this customizable extension, the bug tracking system can be used in ways that do not necessarily need to be foreseen by the developers.