Bug 488358 - Create supplemental cert infrastructure for hwcatalog
Summary: Create supplemental cert infrastructure for hwcatalog
Keywords:
Status: CLOSED DUPLICATE of bug 446164
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Hardware Catalog
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: XINSUN
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-03 21:36 UTC by Gary Case
Modified: 2009-03-04 18:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-04 18:17:27 UTC
Embargoed:


Attachments (Terms of Use)

Description Gary Case 2009-03-03 21:36:36 UTC
Description of problem:

The current method of certification requires supplemental certs to add new/previously untested hardware support to existing certified systems. Once created, there's no easy way to link the supplemental certs to their existing parent systems. I propose that we include an "Add Supplemental Certification" section, similar to the existing "Clone Certification" section, to every closed cert, and change the name of the current "Internal Relationships" field that tracks supplemental certs to "Supplemental Certifications". The "Add Supplemental Certification" section should include a button to create the supplemental cert, a field to describe the purpose of the supplemental cert and an optional field to upload a supplemental results package. Upon clicking the button, BZ would create a new cert entry, copying the Vendor, Make, Model and URL of the original, it would add the description field as a comment, attach the optional package as a results package and link the parent and supplemental cert. 

What would also be helpful is if the supplemental certs were inherited by clones. That way, when you viewed a cloned cert, you could see the supplemental certs linked to its parent cert.

Comment 1 Rob Landry 2009-03-04 18:17:27 UTC

*** This bug has been marked as a duplicate of bug 446164 ***


Note You need to log in before you can comment on or make changes to this bug.