Well, I searched around a bit, and I couldn't find something that seemed to address this. Such a discussion could happen in a number of different places (or I may just be slow), so I could be missing it.
This might be relevant: Martin's blog entry, announcing client-side duplicate checking, suggests if a report duplicates a private bug, the users is prompted to create a new report, that can be duped later:
"For the Launchpad crash database implementation we actually check if the bug is readable by the reporter, i. e. it is private and the reporter is in a subscribed team, or the bug is public; if not, we let him report the bug anyway and duplicate it later through the existing server-side retracer, so that the reporter has a chance of getting subscribed to the bug."
Well, I searched around a bit, and I couldn't find something that seemed to address this. Such a discussion could happen in a number of different places (or I may just be slow), so I could be missing it.
This might be relevant: Martin's blog entry, announcing client-side duplicate checking, suggests if a report duplicates a private bug, the users is prompted to create a new report, that can be duped later:
"For the Launchpad crash database implementation we actually check if the bug is readable by the reporter, i. e. it is private and the reporter is in a subscribed team, or the bug is public; if not, we let him report the bug anyway and duplicate it later through the existing server-side retracer, so that the reporter has a chance of getting subscribed to the bug."
http:// www.piware. de/2011/ 11/apport- 1-90-client- side-duplicate- checking/
This doesn't seem to be what's happening, AFAICT. Of course, that statement could be out of date by now, or I might misunderstand, etc.
Thanks!