Comment 6 for bug 151658

@mark we're proposing to solve this with bug relationships: to have a private and public discussion, have two bugs.
Make the internal one be linked to the public one, or even the staff-only one be linked to a customer-facing one.

The reason we're proposing to do it this way is that it seems highly likely that there will be a cluster of related things folk want when they want partitioned discussions:
 - separate 'in progress' vs 'complete' status
 - different audiences

While we could teach a single bug to manage multiple discussion visibility rules (and a matching UI + bug mail handling) that would be a much bigger project and not solve the case where folk need different completion criteria in the same project.

For instance, consider a bug on the kernel package for folk getting bespoke engineering done; to one of those customers, its done when its shipped, but for the public area - the code change itself - its done when its uploaded to Ubuntu, and there may be N customers all wanted separate 'I'm done now' markers, totally ignorant of each other, and all on the same bug target.