Display the list of official tags under the tags entry widget

Bug #341220 reported by Eleanor Berger on 2009-03-11
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

In addition to the auto-suggesting widget, we want tag entry display a clickable list of available tags, which will be useful for users who aren't familiar with the project.

 * When editing the tags, a floating box will appear below the message box asking the user to use official tags, with a link to expand.
 * Clicking that link will open an overlay, contaiting the text box (which should remain in the same absolute position as the inline text box) and a three-column list of official tags.
 * Tags which currently appear in the textbox appear highlighted.
 * Clicking a highlighted tag unhighlights it and removes it from the textbox.
 * Clicking an unhighlighted tag highlights it and adds it to the textbox.
 * The list should get updated when the textbox is edited directly, so that as new tags are entered they get highlighted in the list (and vice versa).

Changed in malone:
importance: Undecided → Medium
milestone: none → 2.2.3
status: New → Triaged
description: updated
Changed in malone:
milestone: 2.2.3 → 2.2.4
Changed in malone:
milestone: 2.2.4 → 2.2.5

de-targeting for now, since the current ui is probably good enough and we won't have time to do this anyway. we should consider this again after 3.0

Changed in malone:
milestone: 2.2.5 → none
tags: added: bugtag
frizzle21 (frederik-nnaji) wrote :

We should add some sort of support for "types of bugs", as stated in bug 553507 already ( https://bugs.launchpad.net/malone/+bug/553507 ), to improve awareness of issues relevant to me and my individual skillset for contributing solutions.

Gnome and Ubuntu build on contributions from a huge and very diverse community of creative people, who all want to help in improving the quality of the products they use.
To bridge the gap between mere using and actually contributing, finding the type of bugs that matches your individual skill set needs to be facilitated as much as possible. This is where thinking in terms of a large community can come in very handy!

Apport is already an enormously great help and Launchpad itself is a revolution in bringing efforts together..

For a better overview on the launchpad side of things, i envision a form of categorising a bug by its required "areas of contribution". This is very different to looking at "symptoms", since it aims at describing "how to help" instead of "what is wrong".

The place to describe "what is wrong" is the bug description.
Tags should rather address the purpose of a query, which in this case is for people to find suitable issues to help resolve.

types of bugs:

*artwork
*language
*usability
*documentation
*performance
*stability
*security

since "security" is already covered elsewhere, one can consider it redundant in the concept at hand.

especially usability and artwork are issues that often have something to do with visual design, artists should be involved, but artists often don't make it across the barrier of developer parlance..

frizzle21 (frederik-nnaji) wrote :

i guess it's safe to reduce the list to:

*artwork
*usability
*performance
*stability

my thought is to place this redundantly next to tags and also between "Summary" and "Further information" in "Report a bug"

it would make sense as a checkbox list for example
4 supertags that can be easily handled through the tagging infrastructure..

Steve Magoun (smagoun) on 2010-07-19
tags: added: oem-services
Curtis Hovey (sinzui) on 2011-10-01
Changed in launchpad:
importance: Medium → Low
tags: added: javascript
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers