Comment 7 for bug 244998
Revision history for this message
| Scott Kitterman (kitterman) wrote Re: [Bug 244998] Re: No apparent way to reportbugaffecting anotherproject | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
On Friday 04 July 2008 11:33, Björn Tillenius wrote:
> If you read my first comment, you see that I suggested that this is a UI
> issue. It's possible to add another project, but it's not obvious.
The fundamental problem is that you get driven to a page that's about picking
the upstream project for the package when you wanted to select a project
affected by the bug. The entire "force the end user to figure out where
upstream lives before they can do something useful" model is really inside
out.
OK. It is possible. It's not only not obvious, it's completely opaque. That
link looks entirely like you are selcting a different upstream project for
the package, not the bug.
Driving someone who is trying to work on a bug to a package level selection
page is just broken and that's more than U/I.