Comment 13 for bug 531795

Ian - I wrote my comment before your comment showed up.

What you say makes sense. A lower-level issue should not be duplicated to a higher-level project (duplication is bad!).

Isn't it valuable, though, for both the higher-level project developers/users aswell as the lower-level project developers/users to be able to see what issues are with their respective projects, regardless of the location of the issue? After all, both projects are affected by the issue, in one way or the other.

So maybe adding a project to the "Also affects projects"-link should do this:

1. Show up in the issues' list (as TortoiseBZR does in this issue)
2. Show up in the project where the issue is located (QBzr in this case)
3. Show up in the affected projects "known bugs in lower-level projects" (I don't know if there actually is such a list yet - might be an improvement of Launchpad)

I for one would find it usable to know what bugs are known in all of the software my project depends on, instead of having to traverse each issue list in every sub-project (and sub-sub-project ..).