Comment 1 for bug 777853
Revision history for this message
| Robert Collins (lifeless) wrote Re: Better defaults when adding a project to a bug task | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Do you mean product or package? Products are inpendent in Launchpad - folk often *cannot* set priority milestone etc in product A when they can in product B.
could you please describe the problem rather than propose a solution in your bug reports - its easier to understand problems than solutions
For instance, in this one I'm going to guess 'compiz upstream are not taking the priority of the bug for unity into account when they do their own triage'. Which has a related 'when engineering work requires two bugs to be fixed to solve a single problem both bugs need to be clamped to the priority of the problem or the problem is effectively downgraded to the lowest priority'.
Since the latter case can turn up after initial filing, I think it would be better to see if we can solve the problem - particularly with bug relationships (such as dependencies) coming down the track. Further, as phrased this bug asks for a change which would be incompatible with the way upstreams treat launchpad - as their personal bug tracker. In fact its conceptually at odds with the design - we have separate priority etc so that different communities *can* disagree on the severity of an issue.
So, to triage this bug we need to know:
- do you mean packages (if so we're not crossing ownership boundaries)
- if you do mean products, what is the actual problem thats occuring.