Launchpad itself

Can't target existing bugs to another project

Asked by Rebecca Soffe

In essence I need to move bugs from the lookout-canyon series in the Intel project (https://launchpad.net/intel/lookout-canyon) to the dedicated lookout-canyon project, however, I am having troubles with adding the bugs to the lookout-canyon project (https://launchpad.net/lookout-canyon). For example this bug https://bugs.launchpad.net/intel/+bug/1981516 then I go to "Also affects project" then select lookout-canyon project. Then it will not allow me to add a bug, it says lookout-canyon project will not accept a private bug. I have changed lookout-canyon project from private to public to match Intel project but that has not resolved the issue. Also tried making the bug public and that did not work either,

Do you have any ideas on what I could try?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
William Grant
Solved:
Last query:
Last reply:
Revision history for this message
Best William Grant (wgrant) said : 		#1

The "intel" project predates Launchpad's modern (well, 2012-era) project privacy support, and is still configured a bit strangely, so it's not easy for it to interoperate with newer private projects. But there's a workaround.

Projects like lookout-canyon are set to only allow the "Proprietary" information type, which indicates sensitive commercial information that should have appropriate access controls applied. intel predates this functionality, and still uses "Private", which normally indicates things like user data that aren't commercially controlled in the same way. The bug you're trying to move is Private, but needs to be Proprietary since that's all that lookout-canyon allows. You can change this in the top right corner of the bug page.

Additionally, as part of the additional controls that apply to Proprietary, a Proprietary bug can't affect multiple projects simultaneously. This means that once you switch the bug from Private to Proprietary, you'll find that the "Also affects project" link is unavailable. What you'll need to do is remove the "lookout-canyon" series task, then expand the "intel" task and change that existing task to the "lookout-canyon" project.

It may be worth discussing modernising the configuration of the intel project to comply with modern norms, to make this sort of operation easier in the future.

Revision history for this message
Rebecca Soffe (rebeccasoffe) said : 		#2

Thank you that works. Will pass onto the Intel admin that they need to discus modernising the configuration.

Revision history for this message
Rebecca Soffe (rebeccasoffe) said : 		#3

Thanks William Grant, that solved my question.