Bug 741836 - convert vendor name to vendor id in bugs.cf_devel_whiteboard field
Summary: convert vendor name to vendor id in bugs.cf_devel_whiteboard field
Keywords:
Status: CLOSED DUPLICATE of bug 751966
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Hardware Catalog
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tony Fu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 480275
TreeView+ depends on / blocked
 
Reported: 2011-09-28 05:09 UTC by Tony Fu
Modified: 2011-11-08 21:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 741837 (view as bug list)
Environment:
Last Closed: 2011-11-08 21:09:15 UTC

Attachments (Terms of Use)
change cgi and template code to get vendor name from vendors table (4.21 KB, patch)
2011-10-13 11:31 UTC, Tony Fu 		tfu: review? (rlandry)
tfu: review? (wshen)
tfu: review? (pxue)
 Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Tony Fu 2011-09-28 05:09:55 UTC 
Description of problem:


As the part of the vendor cleaning up bug, we need to use vendor id to represent vendor in bugs.cf_devel_whiteboard field (the current code uses vendor name and it causes some duplicate/misspelling vendor).  

We need to change hwcert catalog code to make this change work.
Comment 1 Tony Fu 2011-10-13 11:08:21 UTC 
After the discussion with other team member, we have decided to still using vendor name in bugs.cf_devel_whiteboard field.  Now, the major work will be the migration/audit scripts to correct the vendor name according to the value in hwcert.vendors table and add new vendor entry to vendors table.  While, we still need some changes on cgi files, as well as bug summary template.
Comment 2 Tony Fu 2011-10-13 11:31:52 UTC 
Created attachment 527960 [details]
change cgi and template code to get vendor name from vendors table
Comment 3 Rob Landry 2011-11-08 21:09:15 UTC 
Closing as a duplicate of 752179 of 751966

*** This bug has been marked as a duplicate of bug 751966 ***
Note You need to log in before you can comment on or make changes to this bug.