[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Filipus Klutiero]

https://bugs.kde.org/show_bug.cgi?id=340420

--- Comment #12 from Filipus Klutiero  ---
(In reply to Christoph Feck from comment #1)
> Regarding new users, I do not see this as a problem. If someone picks the
> wrong product, we can reassign it.


You wouldn't be wrong to call me a perfectionist, but if I start filing a
report and find myself unable to answer a question which mandates an answer, I
will give up, not give an answer in which I'm not confident. I see 3 possible
consequences of the current status:
1. Reporters waste excessive time determining the product, and may decide not
to report further issues for that reason.
2. Reporters give up reporting the problem.
3. Reporters select the wrong product. If it takes time for developers to
correct this, that means a duplicate ticket may be opened, again wasting
reporter time. Or worst, it will take more time for product maintainers to be
notified of the issue, which may be fixed late.

> Additionally, many users simply use "kde"
> as the product, because they do not exactly know where the issue is. This
> has served us well in the last years.

Thanks for bringing up this point. But I reported my first issue on this site
in 2006, and I never knew that it was fine to select the kde product when the
precise product is unknown. If you are saying that is the case:
1. It is not clear that the kde product is intended to be used this way. The
product description is simply "General KDE Software problems". Does that mean
problems which affect several applications, such as Qt issues? Is this intended
for requests for new products? This is entirely unclear.
2. If it is fine to use the kde product this way, either:
 1. Such usage should be split to a dedicated product, so triagers only have to
monitor tickets in that product.
 2. Or, if that's its only usage, it should be renamed to something clearer,
like "unknown".
3. The duplicate finder should be taught that when filing an issue in that
"unknown" pseudo-product, all products should be searched. Conversely, when
filing an issue in a specific product, the "unknown" pseudo-product should be
searched.
4. The pseudo-product to select when a reporter has too much difficulty
identifying the precise product should be a lot more clear. It should be
mentioned at the top, or even better - there should be an "I am not sure"
button which allows to skip.


> Not requiring the user to pick any product would increase our workload.


That depends on who "we" are, and which work is being discussed. If "we" are
KDE users:
1. Requiring to indicate the product largely increases the reporting workload
for reporters. I have used KDE for over 15 years. I hit an issue after
switching to Kubuntu 19.04 and to report it to KDE, even though I am a veteran
user who spent several person-months developing KDE and helping KDE users, and
even though I am a senior software developer who somewhat knows C++, I just had
to spend over 1 person-day of work, just to figure out that the symptom
actually resulted from 3 root issues, and locating each of these issues. Even
with my level of knowledge way above the average reporter's, I am not convinced
it was optimal for me to be the one doing all this work.
2. If reporters decide not to report, users will spend more time finding
workarounds for the issues they hit.
3. If reporters decide not to report, resolution is delayed and users will
waste more time dealing with the issues they hit.
4. If reporters refrain from reporting to KDE:
 1. they will report to redistributors, which means reporters waste time filing
duplicate issues.
 2. potential users spend more time and/or have more difficulty evaluating the
quality of KDE or specific KDE products before they pick KDE or choose between
KDE products, as they do not have a complete database of issues to query.
5. If reporters decide to report on alternative channels, such as mailing
lists, these channels are needlessly "polluted", which increases the time
wasted by developers.
6. If reporters select the wrong product, as indicated above, other reporters
may waste time filing a duplicate, and users may waste time with issues fixed
later.

> Btw, I use "https://bugs.kde.org/enter_bug.cgi?product=productname; to
> report bugs. This way, I do not have to pick it from a large list.


I am not sure what your point is. To use that, you need to know the
"productname" (in fact, its codename in this ITS).

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Filipus Klutiero]

https://bugs.kde.org/show_bug.cgi?id=340420

Filipus Klutiero  changed:

   What|Removed |Added

 CC||chea...@gmail.com

--- Comment #11 from Filipus Klutiero  ---
(In reply to Brylie Christopher Oxley from comment #7)
> Ah! Christoph ... and Christophe! Apologies. :)

Christoph, Christophe, Brylie Christopher... for Christ's sake, this is getting
as confusing as KDE's product list!


Thanks for reporting Brylie. Unfortunately as currently titled this ticket's
scope is very wide. Would you mind if this ticket was re-titled to "Simplify
filing the product/component part of tickets"? Anyone is free to open new
tickets about other parts of the reporting process, of course.

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=340420

Christophe Giboudeaux  changed:

   What|Removed |Added

 CC||hvm2...@gmail.com

--- Comment #10 from Christophe Giboudeaux  ---
*** Bug 360400 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Filipus Klutiero]

https://bugs.kde.org/show_bug.cgi?id=340420

Filipus Klutiero  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=360400

-- 
You are receiving this mail because:
You are watching all bug changes.

[bugs.kde.org] [Bug 340420] Make it easier to file issue reports

[Arek Guzinski via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340420

Arek Guzinski  changed:

   What|Removed |Added

 CC||ker...@ag.de1.cc

--- Comment #9 from Arek Guzinski  ---
While i agree that finding the product works well for a specific application,
it does not for bugs that appear in multiple applications (aka bugs in the
frameworks). This is made even worse by having kde 4&5 stuff mixed together.

I propose the following changes:

add a checkbox "show deprecated products"
and/or
add columns to the table, which show in which version of kde it is used

add the Line "If you are unsure, choose kde" at the bottom of the table. This
way it will be visible, after trying to find the right product, but not
encourage people to use it every time.
I remember that i did not file at least one bug in the past, because i could
not find the right product and did not see the "kde" category.

If you click the "search" link from
https://bugs.kde.org/enter_bug.cgi?product=productname , the product should be
preselected.

sometimes i knew which api call causes a problem (through debug output, stack
trace, alook into the applications source code, etc..). However, finding to
which part of frameworks it belongs, is not that easy. it would be great if you
could search for an api call. Or simply find the product name in the api
reference.

-- 
You are receiving this mail because:
You are watching all bug changes.