Users make bugs private because they cannot hide comments

[Curtis Hovey]

The analysis of private bugs with subscribed open teams revealed that 90% were made private to hide the content of one of more comments. Either the user who owns the comment, or the project's owner, driver, or bug supervisor made the bug private. About 15% of these bugs affected more than one projects; such bugs will not be privatable in the near future.

We want to permit the owner of the comment and the users in project roles to hide comment \o/
The permission revision may be trivial, but there UI needs review. For two reasons: 1, we show the hide comment action on every comment, and 2, hidden comments have a florescent yellow background. Both issues were brought up when comment hiding was added and it was decided that it was not important because the issue affects ~registry.

[Martin Pool (mbp)]

i think there are other bugs for the ugly ui

[Curtis Hovey (sinzui)]

You re correct poolie. The two bugs that interest me are bug 782258 and bug 782258. I am writing an email that explains the issue we must solve, what users will probably demand to be solved, and what I want to solve. I hope to set scope to two branches with community members contributing the rest.

[Martin Pool (mbp)]

Thanks sinzui.

I think letting project authorities hide comments is a good idea, but
if we're going to do this more widely and for comments that are less
than outright spam, perhaps we need to think about putting in "comment
removed by ~johndoe" or something, to avoid confusion. Or maybe that
can be separate.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r14324 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/14324>.

[Curtis Hovey (sinzui)]

While the code is in production, we will not let beta-testers use it until we are certain the UI is acceptable.