Existence of private bugs revealed when linked to blueprint

[William Grant]

Private bugs are shown to be linked to blueprints. Everywhere else they are hidden. This is particularly troublesome at the moment given that the preferred bug deletion technique is to mark them private, and the current major spammer likes to link bugs to blueprints.

[Curtis Hovey (sinzui)]

Hi Brad.

Can you investigate this issue. I think we need to know the scope to fix this. We might want to ask the bugs team to handle this.

[Brad Taylor (brad)]

Seems you've got the wrong Brad. I do not work on Launchpad or work for Canonical.

[Brad Crittenden (bac)]

wgrant can you provide an example where you see this bug leakage? I've reviewed the code and it looks correct. I cannot reproduce what you're seeing in LP.

[William Grant (wgrant)]

In the bugs portlet on a blueprint, private bugs are listed as something like “<private bug>”. There's not much information leakage there, but it can be a lot of clutter when a spammer targets one blueprint in particular. Since bugs can't be deleted, the LOSAs unsubscribe everybody and mark them private - but the dozens of “<private bug>”s remain in the blueprint's portlet forever.

[Brad Crittenden (bac)]

The functionality for the blueprints page changed a while back. The problem is no longer present.