BMO/ShadowBugs

shadow bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=801713

in order to help facilitate bugs which have both public and private data, we'll write a "shadow bug" capability into the BMO extension. this is more or less a hack to work around bugzilla's limitation of being unable to restrict comment visibility by groups (beyond the insidergroup function).

the basic idea is to create a custom bug_id field "shadow bug" / "shadows", and link a public bug with a "shadow bug".

• use a bug_id custom field "cf_shadow_bug"
• set the bug-id on the shadow-bug itself (ie. the field tracks "shadows" rather than "shadowed by")
• only allow setting cf_shadow_bug on non-public bugs
• only allow shadowing public bugs
• the 'shadowed-by' link should only be visible to users who have access to the shadow bug
• if the visibility of the shadow bug changes to public, clear the cf_shadow_bug field
• you must be a member of a can_shadow_bugs to set cf_shadow_bug, and for shadowed comments to be visible
  • this is to avoid adding further noise to the bug page
• don't show "shadowed-by" field unless it is set (default bugzilla implementation will always show the field)
• the shadow bug will show comments from both bugs
  • similar implementation to inline history; comments injected by javascript
  • the injected comments will be styled different from normal comments
• set a placeholder in the add_comment textarea on the shadow bug to clearly indicate that it isn't a normal bug, and that public comments should go on the other bug
• set a custom background colour/whatever on the shadow bug
• on the linked bug, ensure the link to the shadow bug is clear