I think this is simply a UI issue. Suggestions on how to make it
clearer is appreciated. If you choose "Also affects projects" from a
source package, we automatically choose the project for you, if there
are packaging links. This is because it's very common to say that a
package bug affects the corresponding upstream project as well.
On the "Also affects project" page there is a way to choose another
project. There is a "Choose another project" link.
On Fri, Jul 04, 2008 at 11:45:13AM -0000, Matthew Paul Thomas wrote:
> That's bizarre.
>
> ** Changed in: malone
> Product: Launchpad itself => Launchpad Bugs
> Importance: Undecided => High
> Status: New => Confirmed
>
> ** Summary changed:
>
> - No apparent way to report bug affecting another project
> + "Also affects project" disallows adding a project depending on context
This is not correct, you can add any project you want from /bugs.launchpad .net/ubuntu/ +source/ mercurial/ +bug/223789.
https:/
I think this is simply a UI issue. Suggestions on how to make it
clearer is appreciated. If you choose "Also affects projects" from a
source package, we automatically choose the project for you, if there
are packaging links. This is because it's very common to say that a
package bug affects the corresponding upstream project as well.
On the "Also affects project" page there is a way to choose another
project. There is a "Choose another project" link.
subscribe bjornt