Bug 176325

Summary:	I should easily view errors in selected component when reporting a bug
Product:	[Community] Bugzilla	Reporter:	Horst H. von Brand <vonbrand>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2	CC:	nelhawar
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-12-02 02:52:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Horst H. von Brand 2005-12-21 14:21:06 UTC

Description of problem:
When one reports a bug via expert (sorry, guided is much too slow for me
here...), one is directed to first search for bugs in the selected components,
and then again select the component for entering the bug. This should be a
one-step process: Give people the option of looking at (recent?) bug reports for
the component when opening the bug entry page, and offer to just move the
comments entered over to another bug on the list.

I'd bet this cuts down on the number of duplicate bugs...

Version-Release number of selected component (if applicable):
Dunno, but at least the bugzilla for Fedora Core and Extras (I probably misfiled
this report horribly)

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 David Lawrence 2008-09-16 16:54:08 UTC

Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.

Comment 2 Noura El hawary 2008-12-02 02:52:58 UTC

in bugzilla 3.2 you don't get directed to find similar bugs at the expert bug entry. so this is resolved.