| Summary: | Possible Duplicates should have the option to show only Bugs from the selected product | ||
|---|---|---|---|
| Product: | [Websites] bugs.kde.org | Reporter: | Barbara Scheffner <laurakittyinka> |
| Component: | general | Assignee: | KDE sysadmins <sysadmin> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | chealer, nate, sheedy, simgunz |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Barbara Scheffner
2017-02-20 06:30:39 UTC
Showing the bugs from all products makes sense sometimes, because the user may not know what is the product related to the bug he is submitting. Example: a bug in the "Open with" dialog should be submitted to frameworks-kio. This is not straightforward, so displaying bug from all the products may be useful. In other cases (like specific applications, e.g., okular) it is obvious what is the product. For me, at least, the products corresponding to the displayed possible duplicated bugs should be displayed in the table by default. In this way, especially in the second example, one can instantly see if the bugs are related to the product he thinks the bug is related to. (In reply to Simone Gaiarin from comment #1) > Showing the bugs from all products makes sense sometimes, because the user > may not know what is the product related to the bug he is submitting. > Example: a bug in the "Open with" dialog should be submitted to > frameworks-kio. This is not straightforward, so displaying bug from all the > products may be useful. Users have to indicate the product, so if they don't know, they're not supposed to be filing a ticket... although ticket #340420 comment #1 claims the kde pseudo-product can be used when users don't know. > [...] > > For me, at least, the products corresponding to the displayed possible > duplicated bugs should be displayed in the table by default. In this way, > especially in the second example, one can instantly see if the bugs are > related to the product he thinks the bug is related to. On that, I have to agree. |