Closed Bug 159948 Opened 23 years ago Closed 23 years ago

after change keyword name, old name still shows up in query results

Categories

(Bugzilla :: Query/Bug List, defect)

2.10
x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 69621

People

(Reporter: ericweb, Assigned: endico)

Details

Using Bugzilla 2.10 installation at Kontiki. Not sure what platform we run it on (have opened call with IT to find out), so marking OS other for now. (Desktop is Win XP Pro, not that it matters.) To repro: 1) create a keyword called "downloadmgr" 2) add that keyword to some bugs 3) go into edit keywords, edit the download mgr, and in the Name field, change "downloadmgr" to "webdownload" and commit your changes The following now work as expected: - If you bring up one of those bugs individually, you see "webdownload" listed in the individual bug's list of keywords - If you query using the new keyword name webdownload, all the appropriate bugs come up in the list HOWEVER, if you query using the new keyword name webdownload and look at the "keywords" column in the query results page: Expected: you see the new keyword name "webdownload" listed instead of the old keyword name "downloadmgr" Actual: you see the old keyword name "downloadmgr" listed instead of the new keyword name "webdownload" Somehow, the old keyword name has been preserved as the query-list display string value, even though the internal database columns seem to have been updated to use the new keyword name internally. Marking minor. Mildly confusing to the BZ user and annoying but functionally harmless.
Kontiki is running Bugzilla on Linux. OS --> Linux
OS: other → Linux
2.10 is really really really really old and has multiple known + published major security bugs. You should update to the recently released 2.16. The automated clearing isn't in 2.16 (see bug 69621), but you should update anyway. You can fix this specific issue by doing a sanitycheck, and then chooing the option to rebuild the keyword cache when offered. (Or load sanitycheck.cgi?rebuildquerycache=1 manually). *** This bug has been marked as a duplicate of 69621 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.