Malone fails to display a bug publically if one of its duplicates is private
Bug #2965 reported by
Christian Reis
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Diogo Matsubara |
Bug Description
Malone fails to display a bug publically if one of its duplicates is private. To verify:
- Create a public bug
- Create a second bug and mark it private
- Dupe second bug to public bug
- Log out
- Visit public bug
You will be asked to log in.
A current example is bug 3436, which is not publicly accessible because its duplicate bug 3438 is private.
Changed in malone: | |
assignee: | nobody → bradb |
status: | New → Accepted |
description: | updated |
Changed in malone: | |
assignee: | bradb → matsubara |
Changed in malone: | |
status: | Accepted → PendingUpload |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I tracked down the problem. It lies on the bug-portlet- duplicate. pt. What would be the correct solution?
1. Should the public bug be marked as a private bug?
This alternative also means that if we mark a private bug a dupe of a public bug that already has any other public bugs pointing to it, all the others should be marked as private too. But what happens if a user marks a private bug a dupe of a public one by mistake? It inadvertently altered the state of the public one to private.
2. Should the public bug be displayed normally but the private one shouldn't be displayed on the duplicate portlet?
I was going for the second solution, but Salgado raised the issue of the first one, so I need some opinions here.
What do you think?