Closed Bug 174725 Opened 22 years ago Closed 18 years ago

Remove keywords, eventually (and use the UI for flags instead)

Categories

(Bugzilla :: Attachments & Requests, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: CodeMachine, Unassigned)

Details

Apparently the new flags are a more general version of keywords and can be used as non-requestable bug keywords. We shouldn't have two systems for this and should aim to remove the old system. One thing that was mentioned was that the keywords have a different UI (text vs. checkboxes I believe) - this is something that needs to be fixed, the UI for each of bug flags and attachment flags should determined by a threshhold of the number of flags there are, which the admin can template-override. Having two different bug fields with different hardcoded UIs is not an appropriate solution.
Summary: Remove keywords, eventually. → Remove keywords, eventually (and use the UI for flags instead)
Keywords have the potential to be an elegant and general solution to the problem of needing further categorization. We are using Bugzilla in our company, and the fact that Bugzilla 2.20 has "classification" just barely make it a good fit for us. We have many programs, with their own products, and the components are often made of assembled sub components from other, ongoing, projects. The flags serve a slightly different solution, in that they can be there to indicate special importance, such as a bug that blocks multiple projects, or is needed for a special timeline. What I'd like to see is for the keywords to become a pulldown, multiple selection list. This interface of typing in a keyword only to have it rejected because of misspelling or non-existance is pure irritation.
QA Contact: mattyt-bugzilla → default-qa
Assignee: myk → attach-and-request
Keywords are clearly still useful (see b.m.o.) and aren't going away any time soon. They are used for different things to flags. Gerv
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.