Bug 51008 – No product code for ROSWELL

Bug 51008 - No product code for ROSWELL

Summary:	No product code for ROSWELL

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	2.8
Hardware:	All Linux

Priority	medium Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-08-06 10:30 EDT by Need Real Name
Modified:	2007-04-18 12:35 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-08-06 10:30:15 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2001-08-06 10:30:11 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.6-ph-01 i686)

Description of problem:
Product code roswell isn't propagated to all the places it needs to be.

How reproducible:
Always

Steps to Reproduce:
1. create roswell bug report.
2. get to "commit" screen.
3. ???
	

Actual Results:  I chose a different version, probably wrong.  (Unless 7.1k
is roswell)

Expected Results:  roswell should probably be consistently listed in all
redhat linux select boxes.

Additional info:

Comment 1 David Lawrence 2001-08-06 12:19:05 EDT

If you chose 'Red Hat Public Beta' as your product then you should not even been
given any other choices except for 'wolverine', 'roswell', and 'fisher'. 7.1K is
the Red Hat 7.1 Korean product and only shows up when you select 'Red Hat Linux'
 as the product. So to reiterate the versions that show up in the bug entry
forms are totally dependent on the product selected from the previous screen.

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