Comment 6 for bug 777824

Jono, the point about it being nuanced on the permissions of the person adding the task is a very good one. Certainly a developer of abc going in and saying "this also needs to be fixed in project xyz" is quite different than a user saying "I think this affects abc, xyz, jkl" - and should be treated differently.

I separated the series task creation defaults, from the package task creation defaults, since it seemed to be a different level of knowledge involved. For series tasks, if a developer of a package says this also affects series l,m,n - they know the code, and no further investigation should be required. Its not a new bug against the package, but rather an extending of scope of impact to other series. If a developer of a package "abc" says this also affects package "xyz" - they are likely to be right, but someone in "xyz" should assess. And knowing the priority of this problem from the other package's sense, makes it more likely to hit the radar for assessment, for those packages which have 100's of new bugs open against them all the time.