bug watch list pushed waaay down when bugs have many subscribers

[Andrea Corbellini]

Recently I received a notification about bug #241305 informing me that a bug watch had been added. So I opened the bug page looking for the bug watch, but it took for me a while to find it under the (long) subscribers list.

The presence of the subscribers list was not the only problem: in fact, I was expecting to find the bug watch not in the sidebar, but in the list of affected projects (which is the place where bug watches are shown when are associated to an upstream project).

[Curtis Hovey (sinzui)]

This is ultimately the same issue as bug 289266. Portlet grow too large. Their size hides information below them, and the information in them cannot be understood in a glance. In general, a portlet should not list more that a few items, perhaps 7, to be understood. Some portlets breakup large lists into smaller ones. In the case of the subscriber and duplicate portlets, this cannot be done...and it should not be tried.

I ultimately care how many duplicates there are; If I want to see them I can expand to portlet or view another page.
In the case of subscribers, I want to know how many people are subscribed. I am only interest in *who* is subscribed when I am choosing to subscribe or unsubscribe someone.

[Andrea Corbellini (andrea.corbellini)]

Despite the length of the portlets is a real problem, I do not think it is the problem causing this bug. What I mean is that I do not think bug watches need a portlet. Because watches bring some useful and interesting information to the bug (e.g. the status on the bugtracker for the upstream/related project), they should be placed in a more visible and intuitive location, like the list of affected projects.

This is also for consistency: I do not see why bugwatches associated to a project are shown in the affected projects, while "orphaned" bugwatches are shown in a totally different location.