Closed
Bug 60769
Opened 24 years ago
Closed 13 years ago
Make bugs in a particular component always confidential
Categories
(Bugzilla :: Administration, task, P3)
Bugzilla
Administration
Tracking
()
RESOLVED
DUPLICATE
of bug 139724
People
(Reporter: ian, Unassigned)
Details
(Whiteboard: [permissions:view] security)
I need to make bugs in a particular component be always confidential to a
particular group. This is for the hixie.ch bugzilla instance.
Reporter | ||
Comment 1•24 years ago
|
||
Will work on this asap.
Reporter | ||
Comment 2•24 years ago
|
||
ok, "ASAP" isn't going to happen. I have no time left for this kind of work.
Assignee: ian → tara
Status: ASSIGNED → NEW
Comment 3•24 years ago
|
||
This is part of what I proposed in bug 39816... hopefully it can make it into
the 2.14 security release.
Depends on: 39816
Whiteboard: security
Updated•24 years ago
|
Target Milestone: --- → Bugzilla 2.14
Comment 4•23 years ago
|
||
Can someone expand on what the intent of this bug is?
Comment 5•23 years ago
|
||
it's been another week with no response... I'd love to write a patch for this
or include it with one of the other patches, but I still have no clue what you
want here. Hixie, you filed this bug, can you explain it in more detail?
Comment 6•23 years ago
|
||
Reassigning to Ian and off 2.14's radar. This is really an enhancement with a
current workaround of putting said componants into their own group. If there's
a strong desire (and more specific information) we can throw it into the 2.16
bucket.
Assignee: tara → ian
Target Milestone: Bugzilla 2.14 → ---
Reporter | ||
Comment 7•23 years ago
|
||
Sorry about this dropping off my radar.
The RFE is that when I file a bug in component X, I want it to (by default) be
set to be confidential for (only visible by) group Y.
Tara's comments suggest this is already possible; is it?
Comment 8•23 years ago
|
||
Yes, but by product, not by component. Turn on the "usebuggroupsentry" param and
create a group whose short name matches the name of your product that you want to
be confidential. The option is still given to the filing user to make the bug
public, but the box for that product group is checked by default. Also, the user
has to be a member of that product group to be able to file bugs against it.
Updated•23 years ago
|
Severity: major → enhancement
Priority: P1 → P3
Target Milestone: --- → Future
Comment 9•23 years ago
|
||
ok, breaking the dependency. No clue what this had to do with bug 39816. This
isn't about specific people seeing confidential bugs, it's about being able to
make a bug confidential by default by component (rather than by product like it
is now).
No longer depends on: 39816
Comment 10•23 years ago
|
||
-> Bugzilla product, Administration component.
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Whiteboard: security → [permissions:view] security
Version: other → unspecified
Comment 11•22 years ago
|
||
Hixie:
Please look over bug 147275 and see if....
(a) The model there addresses your need
(b) The model there would address your need if it were possible to do this by
component as well as by product.
(c) It is a clean miss.
Thanks
Reporter | ||
Comment 12•22 years ago
|
||
That bug is huge, what specifically am I looking for?
Reporter | ||
Updated•21 years ago
|
Assignee: ian → justdave
Comment 13•20 years ago
|
||
Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist. This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it. If you
are dealing with this bug, please assign it to yourself.
Assignee: justdave → administration
QA Contact: mattyt-bugzilla → default-qa
Updated•18 years ago
|
Target Milestone: Future → ---
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•