Bug 2463 – Force guided to people w/o canconfirm

Bug 2463 - Force guided to people w/o canconfirm


Summary:	Force guided to people w/o canconfirm

Status:	NEW

Product:	maemo.org Website
Component:	Bugzilla
Version:	unspecified
Platform:	All All

Importance:	Low normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	Ferenc Szekely

URL:	enter_bug.cgi?product=Website&compone...
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2007-12-02 20:58 UTC by timeless
Modified:	2014-03-08 11:17 UTC (History)
CC List:	3 users (show)

See Also:

Attachments
force guided for people w/o canconfirm (739 bytes, patch) 2007-12-02 20:59 UTC, timeless	Details
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description timeless (reporter) 2007-12-02 20:58:30 UTC

STEPS TO REPRODUCE THE PROBLEM:
1. setup Bugzilla so most users (who are new and don't know what they're doing)
don't have canconfirm

EXPECTED OUTCOME:
expect them to file good bugs

ACTUAL OUTCOME:
they file poor bugs and scare off the developers.

REPRODUCIBILITY:
most reports are unfortunately of poor quality

OTHER COMMENTS:
This can easily be improved by forcing people w/o canconfirm to use the guided
entry form.

Comment 1 timeless (reporter) 2007-12-02 20:59:00 UTC

Created an attachment (id=645) [details]
force guided for people w/o canconfirm

Comment 2 Quim Gil nokia

2007-12-03 07:44:41 UTC

Sounds like a good idea.

Comment 3 Jake Kunnari 2008-01-22 11:16:51 UTC

Marcell: Could you add this patch?

Comment 4 Marcell Lengyel maemo.org

2008-01-22 12:58:13 UTC

I tried but it did not work. Apparently we have a different bugzilla version.

In our enter_bug.cgi there are no such lines as:

 my $product_name = trim($cgi->param('product') || '');
 # Will contain the product object the bug is created in.
 my $product;

Anyhow, I forced the patch and then the new bug page was totally empty. So I
commented out the two new lines.

Comment 5 Karsten Bräckelmann 2008-08-10 23:37:03 UTC

Assigning to me. Proposed to be done during the next Sprint.

Comment 6 Karsten Bräckelmann 2008-09-02 00:56:48 UTC

We'd need to massively clean up the guided form first. Started work on this
with Andre, to enhance the usefulness of the guided form for the average user,
yet do not overwhelm the reporter.

Comment 7 Quim Gil nokia

2008-09-03 09:52:50 UTC

Setting as high since this is committed for Sprint5

Comment 8 Karsten Bräckelmann 2008-09-17 01:23:36 UTC

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

Comment 9 Karsten Bräckelmann 2008-09-17 01:31:04 UTC

See duplicate bug 3721 for an actual walk-through, and the results.

The guided report as-is is unusable for maemo.org. The entire text and hints
need to be adjusted and carefully re-phrased. Some fields like the Build
Identifier need to be removed. This includes code in the template.

Also see bug 3651, questioning this bug. Note, btw, that the strings injected
on submission of the guided form also need to be changed just like that.

The patch doesn't fix this bug.

Comment 10 Karsten Bräckelmann 2008-09-17 01:40:13 UTC

Re-setting priority.

Comment 11 Andre Klapper maemo.org

2008-11-26 17:53:08 UTC

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

Comment 12 Ferenc Szekely maemo.org

2009-10-02 15:14:32 UTC

Karsten is no longer working on maemo's Bugzilla. I could take over the
implementation but we need to design a usable form first. Andre, could we take
this up in the next sprint?

Comment 13 Andre Klapper maemo.org

2009-11-19 16:59:27 UTC

No, let's take a look at this after having 3.4 running.
The current (2.x) guided interface is so extremely ugly that I think that
there's no additional value.

Comment 14 Ferenc Szekely maemo.org

2009-11-25 17:19:33 UTC

Passing the ball back to Karsten ;)

Comment 15 David King 2010-09-14 15:38:21 UTC

As mentioned in comment 13, deferred until after the Bugzilla 3.4 rollout.