Bug 783304 - Extend external bug reference syncing to RHBugzilla
Summary: Extend external bug reference syncing to RHBugzilla
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 21:49 UTC by James Laska
Modified: 2013-09-02 07:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-17 11:17:04 UTC


Attachments (Terms of Use)

Description James Laska 2012-01-19 21:49:36 UTC
As part of the Jira -> Bugzilla migration, support was added to enable syncing between Jira (jboss.org) and bugzilla.redhat.com (see bug#727851).  The comment sync feature could prove tremendously useful for keeping comments in sync between internal Red Hat bugzilla products and community-facing bugzilla products.

While the scenario also applies for RHEL->Fedora, the Red Hat CloudForms product has several internal bugzilla products (CloudEngine, SystemEngine) that frequently clone to/from public facing community projects (aeolus, katello/pulp/candlepin).  Any upstream bugs where CDW/errata tracking is required for a release, are cloned against the appropriate internal bugzilla product.  Unfortunately, it's often cumbersome to keep progress between internal and community bugs in sync.  

It would be very useful for RHEL->Fedora, and CloudForms->[aeolus,katello,pulp,candlepin] to allow:

 1) Enable bugzilla.redhat.com as a valid "External Tracker"
 2) Whenever a bug is cloned, automatically add the appropriate external bugzilla.redhat.com tracker (optional)
 3) Allow "Send Changes" support for bugzilla.redhat.com external trackers

This support would provide bug owner the option of enabling comment synchronization between internal and community bugs.

Comment 1 Simon Green 2012-05-17 11:17:04 UTC
This posses a security issue. If a private bug is linked to a public one, comments that were intended for Red Hat consumption only could be leaked.

  -- simon


Note You need to log in before you can comment on or make changes to this bug.