Bug 355268

It looks like there might be a few issues with navigation on bugs.kde.org

1. When using the "kdenlive" link on https://bugs.kde.org/describecomponents.cgi (browse), you will land on https://bugs.kde.org/describecomponents.cgi?product=kdenlive which is a list of components.

However, when using the "kdenlive" links (one per line) on https://bugs.kde.org/buglist.cgi?component=User%20Interface&list_id=1311254&product=kdenlive&resolution=--- (kdenlive ui issues), you will land on https://bugs.kde.org/component-report.cgi?product=kdenlive (components vs. severity table with links).

Both links should probably lead to the same page, I would much favor the non-table view, although it'd be useful to see how many open tickets are in each of the components.

2. It's impossible to navigate from an issue to the product's page. For example https://bugs.kde.org/show_bug.cgi?id=354835 has the string "kdenlive" in the top overview, but it's not a link. If the viewing user is the ticket owner (and possibly project owners), instead of "kdenlive" they see a drop down menu, so in that case, it couldn't be turned into a link without adding a string.

I'd suggest turning the string into a link and if the user sees the drop down menu, add string+link. I'm not sure either of the links in problem #1 would be sufficient though (see #4 for suggestion).

3. https://bugs.kde.org/query.cgi doesn't allow searching without words but it really should. For example open/kdenlive should lead to https://bugs.kde.org/buglist.cgi?component=User%20Interface&list_id=1311237&product=kdenlive&resolution=---
using " " as a search term will lead to a page saying "You may not search, or create saved searches, without any search terms."

Wordless searches should be allowed, since there is a view that satisfies that search, which also happens to be one of the most important searches (see #4).

4. The most important* views for each product are:
a. ticket pages
b. reporting a ticket
c. list of all open tickets

A list of all unresolved tickets, independent of component should be (part of) the landing page for each product. This means that pressing any link that says "kdenlive" should lead to a view that contains this list: https://bugs.kde.org/buglist.cgi?bug_status=__open__&list_id=1311259&order=Importance&product=kdenlive and in addition it can contain methods to filter the view by component like https://bugs.kde.org/describecomponents.cgi?product=kdenlive does and statistics the way https://bugs.kde.org/component-report.cgi?product=kdenlive does.



Note: the reason I'm aware of the view that shows all open issues for one product is because "kdenlive bugs" google search leads to https://kdenlive.org/bug-reports which has a link to that view as the first link on that page.


*For proof, see the most visible button and the content of the lists on the "issues" landing pages of many bug tracker systems:
- https://github.com/clintbellanger/flare/issues
- https://bugs.launchpad.net/ubuntu/+source/gnumeric
- https://bitbucket.org/rude/love/issues?status=new&status=open (create issue button only visible when logged in unfortunately)
- https://sourceforge.net/p/trigger-rally/bugs/ (create issue button only visible when logged in unfortunately)