No support for bugwatches between Launchpad bugs

Bug #1492415 reported by dann frazier on 2015-09-04
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

When working with Canonical customers, we frequently end up in situations where we have a proprietary bug in our private project, and a separate public bug for the same issue within Ubuntu. The need for this duplication is that the private bug may contain confidential information that needs to remain private, but the public bug is needed for transparent tracking of an issue to be resolved in Ubuntu. Right now there is no way to link the two within launchpad, so we do a lot of manual work to keep the private bug up to date. It would be nice if I could link the bugs in LP and have it moni

It occurs to me that this is a similar use case to having a LP bug monitor the status of an issue in another bug tracker (e.g. debbugs). That is we want our bug to monitor the status of another bug in a read-only fashion. It just happens that our "other bug" is also in LP.

William Grant (wgrant) wrote :

There have been vague plans for some time to have generic "bug linking", where you can see the existence and status of linked bugs if you can see those bugs.

Changed in launchpad:
importance: Undecided → High
status: New → Triaged
summary: - want to have private bugs track public counterparts
+ No support for bugwatches between Launchpad bugs
tags: added: bug-links bugs privacy
William Grant (wgrant) on 2015-09-11
tags: added: bugwatch
Raghuram Kota (rkota) wrote :

Hi William,

Wanted to follow up on this to see if there have been any updates. Number of projects that could benefit from this feature is growing.


Andrew Cloke (andrew-cloke) wrote :

I've also tripped up on this one while executing a number of projects. It would definitely be a good feature to have.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers