Bugzilla – Bug 155846
[AI] warning if a duplicate bug has more open permissions - more bugreports should be public
Last modified: 2009-01-13 00:34:51 UTC
This bugreport is a follow-up and a summary of the http://en.opensuse.org/Meetings/Status_Meeting_2006-03-07 "Bugzilla permissions" topic. Currently, there are several bugs that are not accessable public - for example because they are SLES bugs. This becomes annoying if a bug gets marked as a duplicate, but you can't access the mentioned bug. It was stated clearly that it won't be possible to open all bugreports, but as much as possible should be open. It's also clear that it can't be a pure technical solution, but will need some human interaction. The question: Could there be at least something technical? I'm thinking of a reminder "the duplicate had more open permissions - please consider opening this one too" when marking a bug as duplicate... Is it possible to implement this in bugzilla?
Sonja, can you assign this to the bugzilla team, please?
A bug in a closed product cannot be marked open. This is a Novell policy approved at the Vice President level and enforced by the bugzilla access control mechanism. A bug can be opened to individuals by adding them to the CC list.
(In reply to comment #2) > A bug in a closed product cannot be marked open. This is a Novell policy > approved at the Vice President level and enforced by the bugzilla access > control mechanism. I understand that - but it isn't the answer to the question. If a bug applies to SLES _and_ SUSE Linux, it can be moved to SUSE Linux (which isn't a closed product) and then be opened. As you can see on http://en.opensuse.org/Meetings/Status_Meeting_2006-03-07#Bugzilla_permissions people (from community and @SUSE) want as much "open" bugs as possible - therefore a hint about less permissions of a duplicate would be very useful. Is it possible to include/create such a permission reminder in bugzilla? (Note the difference to automatically opening the duplicate - I understand this isn't possible.) > A bug can be opened to individuals by adding them to the CC list. I'm afraid that's not a realistic solution - most people won't see the bug and therefore can't ask for a CC :-(
Created attachment 75052 [details] confirm-duplicate.html.tmpl Generic (upstream) code that handles this case.
If you wish to submit a patch to the attached code, we will consider it. Note, however, that this is upstream code that Novell has not branched (customized). Therefore, a pretty strong case needs to be made that the upstream code is inadequate. I believe that the upstream code already makes it clear what's going on.
(In reply to comment #5) > If you wish to submit a patch to the attached code, we will consider it. I have never seen this code in action (probably because of too less permissions here ;-) - but I can imagine how it looks. It shouldn't be a problem to add another paragraph that mentions "consider moving the bug to product SUSE Linux" - but it could be difficult to show this only for SLES/novellonly/whatever bugs (I don't know about bugzilla internals to tell). Guessed code (again, I don't know about bugzilla internals): [% IF original_bug_id.product == "SLES" && terms.abug.product == "SUSE Linux" %] <p style="border:2px solid red">Please consider changing the product of [%+ original_bug_id %] to SUSE Linux to allow public access to it.</p> [% END %] Is code like this possible in the bugzilla template? > Note, however, that this is upstream code that Novell has not branched > (customized). Therefore, a pretty strong case needs to be made that the > upstream code is inadequate. I believe that the upstream code already makes > it clear what's going on. Obviously not, as I see lots of "permission denied" messages on duplicated bugs :-( (Of course, I don't know why in every case - but when asking someone @SUSE, I often see "it's a SLES bug"...)
Well, we certainly wouldn't want to hardcode product names here. What would solve our (opensuse.org's) problem would be a merge of permissions, or the possibility of a bug belonging to two products at once. Moving it away from SLES to SUSE Linux is problematic too, as it then doesn't show up in the saved searches of SLES people any more. Adrian, Andreas, this looks like a topic for a project manager meeting to me.
Reassigning to project management: there is no obvious technical solution to the problem, we need to re-evaluate how we handle common code base, cross-product bugs.
For after 10.1...
quote from http://en.opensuse.org/Meetings/Status_Meeting_2006-04-04: skh reported on an Action Item to not close SUSE Linux bugs (open) as duplicates of SLES bugs (closed). Tool support for this problem is difficult, and the issue effects SUSE r&d organisation. This will be discussed at a project manager meeting. All that can be done at present is to ask people to take care when closing bugs as duplicates. A solution should be available by the next round of enterprise products.
Just an idea: Is it possible to create a bugzilla group "opensuse" or "world"? Everybody should be in it, allowing it to open bugs in closed products selectively. Bugs that were reported for an open product and then moved to a closed one (like SL -> SLES) should automatically be in that group.
Let's close this one. This will not happen in the short run and for the future we have to rethink our bugzilla policy, there might be other ways to avoid this.