Bug 240086 - The guided new bug report form is not suitable for feature requests, especially the "steps to reproduce" part
Summary: The guided new bug report form is not suitable for feature requests, especial...
Status: CONFIRMED
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Tru64
: NOR wishlist
Target Milestone: ---
Assignee: KDE sysadmins
URL:
Keywords:
: 298692 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-30 15:21 UTC by uetsah
Modified: 2021-02-07 14:47 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description uetsah 2010-05-30 15:21:14 UTC 
Version:           unspecified
OS:                Tru64

For feature requests, the separation into "Details"/"Steps to reproduce"/etc. is very confusing.
Can't the "Severity" drop-down box be *above* the text input fields, and depending on the selected "Severity" value only the relevant input fields are shown. Would be very easy to implement with jQuery.

Also, it automatically adds the "Reproducible: ..." line to every report even if it's a feature requests, which doesn't make sense.

Reproducible: Didn't try
Comment 1 Diggory Hardy 2010-06-25 09:50:30 UTC 
Or maybe the "severity" selection could be even earlier?

Searching for existing reports on a behavioural change (wishlist or minor bug) usually show a large number of crash reports — these should in theory be easy to filter out when the reporter isn't trying to report a crash!
Comment 2 Jekyll Wu 2013-04-01 15:39:32 UTC 
*** Bug 298692 has been marked as a duplicate of this bug. ***
Comment 3 Jekyll Wu 2013-04-01 15:44:59 UTC 
work around: use the unguided form for feature request, i.e, manually removing the "format=guided" from the URL.
Comment 4 Andrew Crouthamel 2018-11-10 03:21:45 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-21 04:26:25 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Philippe Cloutier 2019-07-18 03:58:59 UTC 
Thanks for reporting uetsah,
Can you indicate the URL you use to report? I am seeing the Severity field above the description, but changing it does not affect the description in any case, so I am confirming this anyway.

There are issues with interface text too - for one thing, the browser title is "Enter Bug".
Comment 7 Philippe Cloutier 2021-01-05 01:22:19 UTC 
Why was this bug's Importance field set to "wishlist"?
Comment 8 Justin Zobel 2021-01-05 01:23:27 UTC 
It's a desire for a change, it's not a bug, so it has been set to wishlist.

On 5/1/21 11:52 am, Philippe Cloutier wrote:
> https://bugs.kde.org/show_bug.cgi?id=240086
>
> --- Comment #7 from Philippe Cloutier <chealer@gmail.com> ---
> Why was this bug's Importance field set to "wishlist"?
>
Comment 9 Philippe Cloutier 2021-01-09 16:26:55 UTC 
Justin, all issues are associated with a desire for a change, whether they are bugs or not. Importance wishlist is reserved to tickets which do not report defects.

This bug's importance is at the very least normal.
Comment 10 Philippe Cloutier 2021-02-07 14:47:29 UTC 
Justin, thanks for restoring the Severity field, or at least giving it an appropriate value.