Product organization in Bugzilla

[Aleix Pol]

On Wed, Sep 14, 2022 at 10:13 PM Nate Graham <nate at kde.org> wrote:
>
> Hello folks,
>
> We often get feedback from bug reporters that it's hard to find the
> right product in https://bugs.kde.org/enter_bug.cgi because it contains
> just a giant intimidating list.
>
> Yes, people can use their browser's search function, and yes, if a bug
> is files in the wrong place, it will be moved to the right place. Still,
> I can't help but admit that this page is quite intimidating, and that
> intimidation may be a barrier to even trying. See
> https://bugs.kde.org/show_bug.cgi?id=340420.
>
> With this in mind, I'd like to propose that we add some grouping on this
> page. Bugzilla provides this feature natively and other FOSS projects'
> Bugzilla instances make use it; see for example:
> - https://bugs.documentfoundation.org/enter_bug.cgi
> - https://bugzilla.redhat.com/enter_bug.cgi
>
> We could do the same, providing a few user-friendly groups for common
> software people use:
>
> - KDE apps
> - KDE Plasma Desktop
> - KDE Plasma Mobile
> - KDE Frameworks
> - KDE Neon
> - Something else (which would contain everything not in any of those groups)
> - Unknown (which would lead to the generic "kde" component
>
> (note: this suggestion is not a formal proposal set in stone, it's just
> an example of a system of grouping we could use)
>
> Thoughts?
>
> Nate

+1 in general

I think that having each product separate should generally be enough.
It should be easy to identify Kate from Krita. KWin from plasmashell
less so.

Something that I think would be good to convey is that it really is
fine if you use the wrong product. I've received problems that were
from tangential components before and it's been fine. It needs
triaging either way.

Thanks for looking into this!
Aleix