Bug 360400

Summary:	Very confusing and hard to navigate long list of products when searching or filing/creating tickets
Product:	[Websites] bugs.kde.org	Reporter:	hvm <hvm2hvm>
Component:	general	Assignee:	KDE sysadmins <sysadmin>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	chealer, sheedy, taurnil.oronar
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description hvm 2016-03-11 07:31:38 UTC

When filing for a bug, the list of products is pretty confusing. I have a hard time finding the name of a product when I know it let alone when I'm not sure which is it. 

The about pages of the applications are not always helpful with this either. 

It would help a lot if there would be more information in the dropdown - official name of the app/product, not just the internal name, version kde it was present in (kde4/kde5, plasma whatever, etc) and searching through all of these.

Thanks!
Voicu

Comment 1 hvm 2016-03-11 07:33:46 UTC

(In reply to hvm from comment #0)
> When filing for a bug, the list of products is pretty confusing. I have a
> hard time finding the name of a product when I know it let alone when I'm
> not sure which is it. 
> 
> The about pages of the applications are not always helpful with this either. 
> 
> It would help a lot if there would be more information in the dropdown -
> official name of the app/product, not just the internal name, version kde it
> was present in (kde4/kde5, plasma whatever, etc) and searching through all
> of these.
> 
> Thanks!
> Voicu

Meant to say, when searching for a bug, i.e. on https://bugs.kde.org/query.cgi

Comment 2 Philippe Cloutier 2019-07-17 21:34:01 UTC

I very much agree with this. With the power JavaScript and the web platform has reached, there should really be a text field to dynamically filter through products, or - even better - the select multiple should be replaced with a fancy drop-down like those allowed by the Chosen jQuery plugin.

This will probably be more complicated since components need to be considered too. Ideally, there would be a single text field where I'd type for example "korgac". If korgac is defined as a product, then that product would come up as the first suggestion. If korgac is instead defined as a component of the korganizer product, then that component would come up as the first suggestion.
I think it would make sense, before attacking this issue, to reconsider the structure of products and components. Many products are small and have a single "general" component. Other products are big and have so many components that some are related; for example, amarok has components "Playback", "Playback/CUE sheet support", "Playback/Replay Gain", "Playback/Streams". Therefore, for a small product like abakus, a single-level categorization system would be better, while for a big product like amarok, a three-level categorization system would be better. So I think it would be best to allow a variable depth. A product could have sub-products, and any sub-product may have sub-sub-products. With this approach, we could put all products/components in a single widget which would ease filtering.

Comment 3 Christophe Marin 2019-07-17 21:36:43 UTC


*** This bug has been marked as a duplicate of bug 340420 ***

Comment 4 Philippe Cloutier 2019-07-18 02:07:34 UTC

hvm, I hope you don't mind, but as this issue affects both ticket search and creation, and as you mentioned creation in your original Description, I am re-titling this ticket so the scope clearly includes filing tickets.

Comment 5 Philippe Cloutier 2019-07-18 02:10:17 UTC

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