Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337712

Summary:	UI Bloopers in guided bug entry form
Product:	Community	Reporter:	Markus Keller <markus.kell.r>
Component:	Bugzilla	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	carsten.pfeiffer, daniel_megert
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:	337245
Bug Blocks:

Description Markus Keller

2011-02-21 07:20:39 EST

UI Bloopers in guided bug entry form, e.g.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT&format=guided :

- Build ID: People often paste just the numbers of the build ID but miss the version and the "I" or "M" at the beginning (e.g. bug 337703)

=> Please add this sentence to the form:
Please copy the complete Version and Build IDs, e.g. "Version: 3.6.2 Build id: M20110210-1200".


- The Description and Steps to Reproduce fields are way too small. We want to encourage people to specify their problem well.

=> Please set the number of rows to 20 each and remove the "height: 200px". Or do it like the normal form, which has 10 rows and onFocus="this.rows=25".

Comment 1 Markus Keller

2011-03-09 06:34:03 EST

> - The Description and Steps to Reproduce fields are way too small. We want to
> encourage people to specify their problem well.

That part is a dup of bug 290887, but this bug has a concrete fix request:

> => Please set the number of rows to 20 each and remove the "height: 200px". Or
> do it like the normal form, which has 10 rows and onFocus="this.rows=25".

Comment 2 Denis Roy

2011-08-12 10:46:06 EDT

*** Bug 290887 has been marked as a duplicate of this bug. ***

Comment 3 Denis Roy

2011-08-12 10:52:21 EDT

I've made the changes in the 4.0 sandbox.  These will be deployed when Bugzilla 4.0 is installed Aug. 28.

25 rows seemed like a bit much, so I put 15.

Comment 4 Eclipse Genie

2014-11-20 13:22:17 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Dani Megert

2014-11-24 08:29:26 EST

Still not fixed.

Comment 6 Eclipse Genie

2016-11-17 13:09:30 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 7 Eclipse Genie

2018-11-25 14:20:18 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 8 Eclipse Webmaster

2018-11-27 15:01:24 EST

After 7 years I'm going to close this as 'wontfix'.

-M.