Closed Bug 129076 Opened 24 years ago Closed 22 years ago

fields prefixed with "bug_" are confusing

Categories

(Bugzilla :: Query/Bug List, enhancement, P4)

2.14.1
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 200837

People

(Reporter: thomas.thurman, Assigned: nobody)

References

()

Details

In the query form, there are some fields that are prefixed with "bug_": * bug_file_loc * bug_severity * bug_status This is confusing; there's no obvious reason why some fields should be "foo" and others should be "bug_foo". For example, a user here, having recently found "resolution" to search on a bug's resolution, was looking for "status" to search on the status field.
Yeah, and bug_file_loc should probably be more descriptive too.
Cleaning this up will magically clean up some of the things I wanted changed in xml.cgi. For that purpose, it would help if all tags were unique and semi-descriptive. We'll need to change bugzilla.dtd after this, too.
I don't see this as being particularly easy if I understand this properly. In particular, this would break bookmarks and stored queries, although we could add backward compatibility cruft. If we didn't care about bookmarks (and we have a specific bookmarking feature on enter_bug.cgi, so we should), an implementation bug #110007 could change stored queries over to referring to field ID rather than name, without needing the cruft.
Priority: -- → P4
Target Milestone: --- → Future
This is kind of like bug #200837.
Severity: trivial → enhancement
Assignee: endico → nobody
That's true. *** This bug has been marked as a duplicate of 200837 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
clearing target on worksforme/duplicate/invalid so they'll show up as untriaged if they get reopened
Target Milestone: Future → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.